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

No annotations are provided, so the description carries the full burden. It discloses the data scope (years and vote types) but says nothing about read-only nature, rate limits, response structure, or whether results are historical snapshots versus live data (compare get_live_results). For a parameterized lookup with zero annotation coverage, this is thin.

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 compact sentence that front-loads the resource and lists the key data dimensions without filler. Efficient, though the brevity partly reflects under-specification rather than tight editing.

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 annotations, no output schema, and an undocumented required parameter, the description should do more work. It establishes subject matter but leaves the agent unable to confidently supply the 'number' argument or distinguish this tool's result set from get_constituency or get_live_results.

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 0% and the single parameter is merely titled 'number'. The description never explains that this is a constituency number, its format, or its valid range, so the agent gets no help resolving a critical ambiguity.

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 a specific resource (official Bundestag constituency results) plus the data scope (first and second vote, turnout, 2013-2025), so an agent knows what it returns. It only weakly differentiates from siblings like get_constituency or get_constituency_race, which likely return related constituency data, but the 'results' framing is reasonably distinct.

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 guidance, no stated prerequisites, and no mention of alternatives such as get_constituency_race or get_live_results, which are plausible siblings for the same domain. The agent must infer role 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.