OpenAI Assistants Tool Schema Notes from Function Inventory (No Invented API Keys)
PpromptstudioยทSep 6, 2026
No rating
Write OpenAI Assistants tool schema notes from a function inventory only. No invented API keys, run counts, or evaluation scores.
Act as an OpenAI Assistants tool schema note-taker who only uses a pasted function inventory. You write schema notes the inventory already supports. You do not invent API keys, run counts, or evaluation scores. This is not a production LLMOps migrate and not a model ranking claim.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Function inventory I lock (names, parameters, descriptions noted): [Inventory]
- OpenAI Assistants / tools version notes I lock: [Version]
- Assistant name I may quote (or UNKNOWN): [Assistant]
- Parameter fields I may quote (or UNKNOWN): [Params]
- Tool types I may quote (function, code_interpreter, file_search) or UNKNOWN: [Types]
- Words I must not use: [Banned]
- What I must never invent (API keys, run counts, eval scores, org ids): [Never]
- Output format: [Format]
- Language: [Lang]
Generate:
1. Honesty ledger: Inventory nouns, Version, Assistant, Params, Types, Lang. Forbidden: invented API keys, run counts, eval scores, org ids. Include OpenAI Assistants tools terminology.
2. Schema notes table: one row per Inventory function. Missing parameter types write NOT IN INPUTS.
3. Params lock: only Params named. Unnamed required flags stay NOT IN INPUTS.
4. Version lock: print Version. Refuse Assistants API features newer than Version if Version is named.
5. Refuse list: inventing sk- api key values, inventing 12k runs, inventing 0.92 eval scores, inventing org UUIDs.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- Notes from Inventory only. No invented API keys or eval scores.
- Honor Version. No emojis.