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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety and idempotency profile is covered. The description adds the useful detail that transcript retrieval is opt-in via include_transcript, but says nothing about the default result's size, pagination, or performance cost of pulling a full transcript.

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?

Single sentence plus one opt-in clause, front-loaded with the primary purpose and the most important parameter toggle. Nothing is wasteful and the core value proposition leads.

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 tool whose annotations carry the safety profile and whose schema fully documents both params, the description is nearly complete — it explains the returned content and the transcript option. Minor gap: no mention of behavior when meeting_id is invalid or not found.

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 both parameters are fully documented in the schema including the default (false) and the cross-reference to list_meetings for meeting_id. The description restates the include_transcript behavior but adds no format or constraint detail beyond the schema, so baseline 3 applies.

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+resource ('Get one meeting in full') and enumerates what is returned (summary, key decisions, action items, what changed), which distinguishes it from list_meetings and search_meetings. An agent knows exactly what this retrieves without opening a 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?

Usage is implied by 'one meeting' with a required meeting_id, positioning it against list_meetings. However, it never explicitly states 'use this when you have a meeting_id' or names alternatives like search_meetings, so guidance remains inferential rather than explicit.

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