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

With annotations already indicating readOnly and idempotent behavior, the description adds valuable context: the 'content_missing' status meaning, the condition about queryable imports, and the exact cost and payment protocol. It also warns that a broken record should not be reported as an empty meeting, which is a meaningful behavioral nuance beyond the annotations.

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 three sentences with no filler: it states the action, gives the usage context, flags an important status edge case, and mentions the cost. Every sentence adds unique value, and the most important information is front-loaded.

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?

Given the rich input schema, output schema, and annotations, the description covers all essential operational aspects: what it fetches, when to call it, how to interpret an edge-case status, and the cost. Nothing an agent needs to correctly invoke this tool is missing.

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?

The input schema already documents all three required parameters with 100% coverage, so the description is not required to add parameter details. It does not introduce any new semantic nuance beyond what the schema already provides. Baseline of 3 is appropriate because the schema fully carries the burden.

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 ('Fetch') and identifies the exact resource ('a single meeting by meeting_id'), including the key behavior of returning the full transcript when queryable. It clearly distinguishes this tool from meetings_search and meetings_list by focusing on retrieval of one identified meeting rather than discovery.

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?

It explicitly says to use this tool after meetings_search has identified the meeting, giving a clear ordering context. It also explains how to interpret a 'content_missing' status, preventing incorrect reporting. It does not explicitly mention when not to use it or name alternative tools, but the usage context is sufficient and clear.

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