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

Annotations already cover readOnly/non-destructive, but the description adds genuine interpretation context beyond them: no slide rating because a score hides meeting provenance, and a quiet slide means no reaction, not agreement. It also states the evidence is excluded from decks/exports. This is meaningful behavioral disclosure, though it doesn't cover pagination or scopic limits.

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?

Four short, front-loaded sentences with essentially no filler; the core purpose leads. The elliptical phrasing is a minor cost but nothing is wasted.

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 explained, and annotations carry the safety profile. The description fills the key interpretive gap (quiet is not agreement; no ratings) needed to use the evidence correctly. It could add a pointer to sibling tools but is otherwise complete.

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?

Only one parameter (companyId) exists and schema coverage is 100%, so the schema already documents it as a UUID wrapper. The description adds no meaning about the parameter, so the baseline 3 applies when the schema does the heavy lifting.

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 communicates that this returns per-slide reaction/resonance data with quotes from rooms where the deck was shown, but it does so elliptically ('what it produced in the rooms it was shown in') rather than naming a clear verb+resource. It does not distinguish itself from siblings like fundraising_get_deck or fundraising_get_memo_engagement. An agent can infer the resource but not cleanly separate it from adjacent tools.

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 explicit when-to-use guidance or comparison to alternatives such as get_deck or get_memo_engagement. The only orienting line ('never travels in a deck or an export') concerns where the output does not appear, not when to select this tool. Usage is implied at best.

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