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

With no annotations, the description carries the full behavioral burden. It usefully discloses the returned content (medians, uncertainty bands, seats, majorities, a data-quality indicator), but says nothing about read-only nature, required ID format, behavior on unknown IDs, or whether results are live versus archived.

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 telegraphic sentence with zero padding, front-loading the scope ('One German election') before the payload fields. It is a noun phrase rather than a sentence, which is terse but still readable.

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?

For a simple single-parameter lookup with no annotations and no output schema, listing the returned metrics covers a good share of what an agent needs. However, the missing ID format and the absence of any error or availability behavior leave real gaps.

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 required parameter election_id has no title-level explanation. The description implies an identifier selects one election but never gives its form or an example, leaving the only parameter effectively undocumented in both schema and description.

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 phrase 'One German election' states the resource and scope, and the enumerated fields (vote share median, 95 percent band, seats, majorities, data quality) make clear this returns a single election's aggregated result. It implicitly contrasts with list_elections, but does not explicitly distinguish itself from get_election_statistics or get_live_results.

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 statement of when to use this tool versus siblings such as list_elections, get_election_statistics, or get_live_results. The only usage signal is the singular 'One ... election', which the agent must infer means it requires a known election_id rather than a filter.

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