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

Adds substantial context beyond the readOnly/idempotent annotations: pagination contract, untrusted-content handling, empty-content semantics, the caveat that follow-up drafts may not have been sent or saved to CRM, and an explicit enumeration of side effects that are NOT triggered. This is behavior an agent could not infer from annotations alone.

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?

Front-loads the purpose and contents, then proceeds through usage, pagination, safety and scope in compact sentences. It is dense and longer than typical, but nearly every clause carries actionable information; only the summarization-style guidance is mildly expendable.

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 no output schema, the description still communicates the return payload (summary, transcript, chat, notes, drafts) and its pagination and emptiness semantics. For a read-only retrieval tool this covers everything an agent needs to call and interpret it correctly.

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 0%, so the description must carry parameter meaning. It clarifies query, the offset/nextOffset pagination loop, and locale via 'user's language', but says nothing about limit or the roomId format beyond the list_meetings pointer. Partial compensation for a 5-parameter tool.

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 ('Catch up on an owned meeting') and enumerates exactly what is retrieved: saved summary, speaker-labelled final transcript, chat, notes and follow-up drafts. This content bundle distinguishes it from the generic get_meeting sibling without the agent opening either 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?

Explicitly routes the agent: use list_meetings to select the room, ask when multiple meetings match, and use query for a specific topic. The pagination instruction ('follow nextOffset before claiming to have reviewed the whole meeting') further qualifies correct usage.

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