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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only lookup, whether any permissions or rate limits apply, or what form the returned statistics take; it only implies a read via the verb 'statistics'.

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: resource first, then the available breakdowns. It is terse without being padded, though the terseness contributes to the gaps elsewhere.

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, no annotations and a 0%-documented parameter, the description should explain the return shape and the accepted 'kind' values. It provides only a topic list, leaving an agent guessing at invocation format and response contents.

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 0% and the single required parameter 'kind' has no enum and no description. The four listed topics (postal-vote, ticket-splitting, age-groups, turnout) appear to be the accepted values, partially compensating, but the description never explicitly ties them to 'kind' or states whether the parameter takes one value or many.

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 ('Federal election statistics') and enumerates four sub-topics, which is more informative than a bare tautology. However, it never clarifies the relationship to close siblings such as get_election, get_federal_trend, get_latest_polls or get_constituency_results, so an agent cannot confidently distinguish this tool from them.

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 when-to-use or when-not-to-use guidance, and no alternative is named despite a crowded sibling set covering elections, polls and trends. The agent must infer selection from the name alone.

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