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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint: false. The description adds useful behavioral context beyond those flags by stating data provenance (Wikidata and official election commission records) and detailing the returned fields and status vocabulary. Nothing contradicts the annotations.

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?

The description is three sentences, starts with the operation and resource, and efficiently covers output, filters, a use case, and data provenance. Every sentence earns its place, with no repetition of the title or schema details.

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 read-only list tool with fully documented optional parameters, an output schema, and safe annotations, this description is complete. It covers the resource scope, return content, filter options, a concrete use case, and data provenance, so nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3. The description briefly summarizes the filterable dimensions (country, status, year range) and highlights the 'upcoming' status use case, but it does not add substantive parameter semantics beyond what the schema already provides.

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 verb ('List') and a well-defined resource: presidential, parliamentary, and local government elections across all 54 African countries. It also enumerates the returned fields (scope, status, dates, country), making the operation concrete and distinct from the sibling africa.* tools.

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?

It provides a concrete scenario: 'Use status="upcoming" to find upcoming African elections relevant to political risk analysis or investment due diligence.' This tells agents when the tool is valuable, but it does not explicitly discuss alternatives or exclusions; however, no sibling tool covers this exact domain, so the guidance is sufficient.

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