get_realtime_session_transcript

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Get...'. It does not explain what the returned transcript contains, whether the session must be completed, how the transcript is formatted, or whether there are any side effects. 'Get' implies a read operation, but key behavioral context is missing.

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?

The description is a single, focused sentence with no filler, repetition, or unnecessary detail. It is appropriately sized for the simple retrieval operation and front-loads the core action and resource.

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?

There is no output schema and no annotation coverage, so the description needs to explain what a transcript response contains or how this tool behaves. It does not. While the parameters are fully covered by the schema, the missing return-value semantics and lack of sibling differentiation leave the definition incomplete for an agent choosing and invoking it correctly.

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 100%, so the three parameters are already documented as account ID, app ID, and session ID. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 clearly states a specific verb ('Get') and resource ('Realtime Kit session transcript'), which is distinct enough from sibling tools like get_realtime_session and get_realtime_session_summary. It is not vague or tautological, though it relies mostly on the tool name to make the distinction.

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?

No guidance is given about when to use this tool instead of related alternatives such as get_realtime_session, get_realtime_session_summary, or list_realtime_sessions. The description only implies the obvious use case of getting a transcript and does not mention prerequisites, exclusions, or alternative routing.

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