openai_create_realtime_client_secret

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: the credential is ephemeral ('short-lived') and the main API key is never exposed in the response. It omits auth requirements, what the secret grants, and how expiry interacts with the expires_in_seconds default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the key security property. Nothing is wasted, but the brevity comes at the cost of substance rather than being achieved through efficient compression.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, so that need not be described. However, a 5-parameter tool with 0% schema coverage, no annotations, and a free-form session_json string requires far more explanation than this two-sentence description supplies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, so the description must compensate and does not. 'Short-lived' hints at expires_in_seconds, but model, session_json, session_type, and safety_identifier get no explanation at all — critically, the format and expected contents of session_json are left completely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Create a short-lived Realtime client secret.' This is enough to distinguish it from most siblings (create_response, create_chat_completion), though it does not explicitly contrast with the nearby openai_create_realtime_translation_secret beyond the word 'Realtime'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the sibling secret/session tools (openai_create_realtime_translation_secret, openai_create_live_session). The agent must infer from the name that this is for bootstrapping a browser/mobile Realtime connection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.