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

Annotations already declare readOnlyHint=true, and the description goes further by specifying the transcript includes all segments, speakers, and timestamps. This adds behavioral context about the output beyond the annotation, though it does not cover pagination, limits, or error behavior.

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, efficient sentence that front-loads the core purpose and includes the most important output details. There is no repetition of schema or annotation information and no wasted words.

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?

For a read-only tool with one simple parameter and no output schema, the description covers the essential behavior and return contents. It is only slightly incomplete because it does not suggest how to obtain the sessionId or explicitly route the agent away from sibling tools like get_session.

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%, and the description does not explain the sessionId parameter beyond implying it identifies the session. It does not clarify the expected format, how to obtain it, or any constraints, so the description fails to compensate for the schema's lack of parameter documentation.

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 uses a specific verb ('Returns'), names the resource ('full transcript'), and specifies the scope ('for a session') plus content details (all segments, speakers, timestamps). This clearly distinguishes it from sibling tools like get_session.

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?

The description makes it clear what the tool returns, so an agent can infer when to use it for transcript retrieval. However, it does not explicitly state when to use this tool instead of alternatives such as get_session, nor does it provide exclusion criteria.

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