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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavior beyond annotations: it confirms the tool does not create/edit/delete meetings and explicitly states unknown ids return an error. This error-handling detail is genuinely useful context not present in 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?

Every sentence earns its place: the first defines the read payload and equivalence to get_meeting, the second explains the connector rationale, the third provides usage constraints and alternatives, and the fourth states safety and error behavior. No fluff or redundancy.

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?

Despite having no output schema, the description specifies the return content (notes, action items, participants, speaker-labeled transcript), the input source, the error case, and the non-mutating behavior. Combined with rich annotations, this is enough for an agent to call the tool correctly and understand what to expect.

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%, with the parameter already documented as 'Meeting id from search, e.g. "mtg-1786560198190".' The description reinforces using an id from search and mentions error behavior for unknown ids, but adds no substantive meaning beyond the schema. Baseline 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 states a specific verb ('read') and resource (one meeting's notes, action items, participants, and speaker-labeled transcript), and clearly differentiates this tool from get_meeting, search, and search_meetings. It explains that fetch is a connector-required alias, so there is no ambiguity about what it does.

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 explicitly says when to use fetch (only because ChatGPT's connector requires that name), when to prefer get_meeting ('other clients should call get_meeting'), and what not to use it for ('Do not use to find a meeting by topic'), naming the alternatives search and search_meetings. This gives an agent complete routing guidance.

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