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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that: the REVISION_CHANGED error for a changed meeting and the fact that a part id embeds the meeting revision, both of which affect how the caller handles results.

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?

A single front-loaded sentence led by the imperative 'Use this to open...', with the payload description following. Dense but every clause (document kinds, id semantics, error code) carries information; no filler.

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?

An output schema exists, so return values need not be described, and the description still covers the two result shapes at a high level plus the id-format caveat and error behavior. For a one-parameter read tool with full annotation coverage, nothing essential 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?

Schema coverage is 0% (the id property carries no description), so the description must compensate, and it does: it explains that the id may denote either a meeting or a transcript part and that a part id includes the meeting revision. That is materially more than the bare 'string, 1-200' schema constraint.

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 gives a specific verb and resource ('open one meeting document by its id') and enumerates the two document kinds it can return (meeting overview vs. a single transcript part). It is clear on its own, but never names the overlapping sibling meetnotes_get_transcript, so an agent cannot fully disambiguate from the text alone.

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?

'Use this to open one meeting document by its id' implies the usage context but states no when-not condition and no alternative. Given a sibling named meetnotes_get_transcript, the absence of any routing guidance between the two leaves the choice to inference.

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