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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not mention the default exclusion of 'noted' decisions, pagination via cursor/limit, or that results are scoped to one meeting — behavioral facts an agent needs and that only the schema hints at.

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 well-formed sentence with no filler, front-loading the operation and its scope. However, its brevity comes at the cost of the operational detail the tool actually needs.

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 7-parameter, paginated, filterable read tool with no output schema, the description is too thin. It never mentions the pagination loop, the default decision-type filter, or how the filters combine, leaving the agent to reconstruct behavior from the schema alone.

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 71%, and the description supplies no parameter meaning at all. It does not explain q's semantic matching, agenda_item's prefix behavior, the 50/200 limit bounds, cursor continuation, or the fact that decision_type defaults to everything except 'noted' — leaving the description unable to compensate for the coverage gap.

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 clear verb (List) and resource (meeting decisions), and enumerates the outcome categories — agreed, approved, noted, rejected — so an agent knows it returns decision records rather than raw meeting content. It does not distinguish itself from siblings like get_meeting or list_documents, which may also surface meeting outcomes.

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?

There is no guidance on when to choose this tool over alternatives such as get_meeting, nor any prerequisite or exclusion information. The agent must infer usage entirely from the name and schema.

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