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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: it returns an error object when the meeting is not found, and it warns that the transcript fetch can be long.

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?

Two short sentences, front-loaded with the core purpose, followed by the single optional-flag instruction and the error behavior. No filler or repetition.

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?

With a full output schema, return shape need not be explained, and annotations carry the safety profile. The description covers the error case and the optional transcript, leaving only minor gaps such as whether 'topics' differ from the transcript and any rate/length limits.

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 100%, so a baseline of 3 applies. The description goes beyond the schema by explaining the intent of include_transcript — retrieving the complete transcript specifically for direct quotation — which tells the agent why it would pay the size cost.

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?

States a specific verb and resource ('Get a single meeting') and names the payload ('full AI summary and topics'), which cleanly separates it from list_recent_meetings and the search_* siblings. An agent can tell what it will receive without opening the schema.

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 gives a clear conditional for the optional flag ('Set include_transcript=true to also retrieve the complete transcript... for direct quotation'), which is real usage guidance. But it never states when to call this tool versus the search/list siblings or where the required meeting_id comes from in the description itself (that hint lives only in the schema).

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