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

The annotation readOnlyHint=true already declares this as a safe read operation. The description adds the detail that the address must be a 'registered U.S. voter address', which is a useful eligibility constraint but not a behavioral trait like side effects or error handling. No contradiction with 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 a single, front-loaded sentence that conveys the core purpose without extraneous words. Every piece of information (election info, polling location, early vote sites) adds value.

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 read-only lookup tool with one parameter and no output schema, the description is sufficiently informative. It mentions the key return categories (upcoming elections, early vote sites) and the input constraint (registered U.S. voter address). It could be more explicit about failure modes (e.g., unregistered address), but the tool's simplicity keeps the gap small.

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% for the single parameter 'address', and the description restates it as 'registered U.S. voter address', adding minimal beyond the schema. The baseline of 3 is appropriate since the schema already documents the parameter adequately.

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 clearly states the tool's function: 'Get election and polling location information for a registered U.S. voter address'. It uses a specific verb ('Get') and resource ('election and polling location information'), and the scope ('for a registered U.S. voter address') distinguishes it from sibling tools like get_representatives or get_member.

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 description implicitly conveys when to use the tool: when you need election or polling location data for a voter address. It does not explicitly mention alternatives or exclusions, but the context is clear enough. With a single parameter and read-only semantics, additional usage guidance is not critical.

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