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

Annotations already carry readOnly/idempotent/openWorld=false, so the safety profile is covered. The description adds genuinely useful context beyond that: it returns a paged list, the next_cursor mechanism, per-field types and semantics (votes = votes where both parties voted yes or no), and an attribution obligation. It omits rate limits and error behavior, but for a read-only aggregate tool this is a solid disclosure.

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-loaded with the one-line purpose, then pagination, then a compact field list, then the attribution line. Every sentence earns its place, and the dense field enumeration substitutes for a missing output schema rather than padding.

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 usefully enumerates the returned fields and their meanings, plus pagination and attribution — enough for an agent to interpret results. The main gap is selection guidance relative to party_attendance, but the data-shape completeness is strong.

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%, so the baseline is 3. The description reinforces the cursor/pagination parameter (oddly calling it next_cursor rather than the schema's 'cursor'), but adds no meaning for limit, party, or party_in beyond what the schema already documents.

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: how often parties vote alike, which is a distinct analytical measure from the sibling party_attendance (which would be about presence/participation). It doesn't explicitly contrast with that sibling, but the title and name pin the purpose down unambiguously.

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?

It explains pagination mechanics ('pass next_cursor to get the next page') but gives no guidance on when to use this tool versus party_attendance or any other sibling, and no preconditions or exclusions. The closest thing to usage guidance is the pagination note, which is procedural rather than selection guidance.

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