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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. With no output schema, the description earns credit by spelling out what comes back (per-radar headlines, human and AI vote tallies, each group's leader, agreement flag), which is exactly the behavior an agent cannot get from structured fields.

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?

Two sentences, front-loaded with the resource and its contents, then the optional parameter. The middle clause listing return fields is dense but every element is informative; no filler.

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?

Single optional parameter, read-only annotations, and no output schema — the description fills the one real gap by describing the return payload and the date default. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so baseline is 3, and the description goes slightly beyond by framing the date as optional-for-past-days, implying that omitting it returns today's ballot. The YYYY-MM-DD format is repeated from the schema rather than adding new syntax detail.

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 names the resource precisely ('Today's ballot and results') and enumerates the payload: candidate headlines per radar, human and AI vote counts, group leaders and agreement. This clearly separates it from siblings like vote_top_story (casting a vote) or get_radar (radar metadata), though it does so implicitly rather than by naming an alternative.

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?

Usage is only implied: 'Optional date (YYYY-MM-DD) for past days' tells the agent it defaults to today and can look backward, but there is no explicit statement of when to call this versus vote_top_story or get_question_status. The agent must infer the read-vs-vote split from the names alone.

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