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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description is not asked to carry the safety burden. It still adds genuinely useful context beyond annotations: results are 'latest' (freshness), carry source dates (traceability), and may be provisional (reliability caveat). No mention of pagination or size, but with no parameters there is little pagination concern.

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 front-loaded sentence with no filler. Every element (compact, latest, results + averages, source dates, provisional) conveys distinct information.

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?

There is no output schema, so the description must convey return content, and it partly does: results, averages, dates, and status. However, it never clarifies the scope of 'latest' — whether it covers one election, all tracked elections, or a fixed recent window — which is the main ambiguity an agent would face for a zero-argument summary tool.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing the description could clarify about inputs, and it correctly avoids inventing any.

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 resource (latest election results and polling averages) and a distinguishing form factor ('compact') that separates it from detail-oriented siblings like get_polls, get_election, and get_analytics. It stops short of naming those siblings, so the differentiation is implicit rather than explicit.

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 word 'compact' implies this is the overview entry point rather than the detail tools, but there is no explicit when-to-use or when-not-to-use guidance and no sibling is named. An agent must infer that details live in get_election/get_polls.

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