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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds meaningful operational context: public unauthenticated access and a rate limit of 60 requests per minute per IP. It also restates zero state mutation, but the added auth and rate-limit details earn credit beyond the annotations.

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?

The opening analytical sentence is well front-loaded, but the definition contains boilerplate: the 'when to use' clause repeats the tool name, the parameter line duplicates the schema, and the return sentence is generic ('matched records or computed metrics') rather than tailored to consensus analysis.

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 one-parameter read-only tool with no output schema, the definition covers purpose, alternatives, safety/auth/rate-limit behavior, and a high-level return description. It is complete enough for correct invocation, though the return description remains generic.

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 100% and the single poll_id parameter is fully described in the schema. The description only repeats that poll_id is required, adding no syntax or format detail beyond the schema; 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?

The first sentence names a specific analytical action—analyzing vote distribution and calculating the optimal meeting slot—and enumerates concrete outputs such as percentage agreement, voter breakdown, and AI scheduling recommendations. It clearly separates the tool from create_meeting_poll and submit_participant_vote, which are named as alternatives.

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?

The description explicitly names both sibling tools and instructs not to use this tool when a more specialized one fits better. However, the positive 'when to use' clause is largely circular ('when you specifically need to execute get_poll_consensus'), so it does not give a concrete scenario beyond the purpose sentence.

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