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

Rich annotations (readOnly, idempotent, non-destructive, closed-world) already carry the safety profile, so the description earns credit by disclosing the shape of the payload: votes, seats, turnout and editorial blocs. It does not address the 'latest' default behavior, but the schema does.

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 dense sentence with no filler, and the scope ('for one election') is front-loaded alongside the data returned. Nothing could be removed without losing 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?

For a one-parameter read with complete annotations and no output schema, the description tells the agent both what entity it targets and what fields come back. The only gap is routing guidance relative to list_elections and the elections-discovery workflow.

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?

There is a single parameter at 100% schema description coverage, with the schema already explaining the 'latest' / knesset-ID / bare-date ambiguity. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 with concrete payload contents (party votes, seats, turnout, editorial blocs) and scopes it to 'one election', which implicitly separates it from the plural list_elections. It stops short of explicitly naming a sibling, so it is clear but not fully differentiated.

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 phrase 'for one election' implies the use case (single-election detail rather than enumeration), but there is no explicit when-to-use or when-not-to-use guidance, and no mention that list_elections is the route for discovering election IDs. Guidance is inferable only.

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