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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is covered. The description adds useful scope context by stating coverage starts in 1991 for parliamentary and 1992 for presidential elections, but it does not describe pagination, result volume, or ordering.

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 fragment covering both election types, their start years, and the returned fields, with no wasted words. It is front-loaded and scannable, though the verbless fragment style makes it read as a dataset blurb rather than a tool instruction.

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-optional-parameter read tool with rich annotations and no output schema, the description is adequate but minimal. It omits how this differs from get_election_results, which is the most important missing context given the sibling list.

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 100% and the enum is documented in the schema itself ('ns = parliament, pr = president'), which the description merely restates. With a single optional parameter fully documented, the baseline of 3 applies; the description adds nothing new about the parameter.

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 identifies the resource (parliamentary and presidential elections) and the fields returned (date, voters, turnout), but never states an action and does not distinguish it from the sibling get_election_results. An agent can infer this is a listing of election events, yet the boundary with the sibling tool is left ambiguous.

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 mention of prerequisites, and no reference to alternatives such as get_election_results. The temporal scope hints at coverage but says nothing about when an agent should pick this tool over its sibling.

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