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

Well beyond the annotations (readOnly/idempotent/openWorld/non-destructive), it discloses data provenance (EAC 2024 survey, November 2024), that answers are self-reported and coded, that vendor counts overlap and must not be summed, and precise linguistic constraints on what the agent may claim. This is exactly the interpretive context annotations cannot provide.

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?

Front-loaded with the lookup operation, then layered caveats. Every sentence carries substantive interpretation guidance, though the block of caveats is dense and could be tightened marginally.

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?

With no output schema, the description adequately conveys what comes back (coded equipment answers with make/model and MORVS-curated vendor labels) and how to interpret gaps. Minor omissions like pagination/limit behavior and the sibling-tool boundary keep it from a 5.

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 restates state code and jurisdiction name substring (adding only the 'literal' qualifier) and says nothing about the limit parameter beyond what the schema documents.

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?

Uses a specific verb ('Find') and resource ('jurisdiction') and states the lookup key (two-letter state code plus literal jurisdiction name substring) and the returned payload (coded equipment answers from the 2024 EAVS with make/model and vendor labels). It doesn't explicitly distinguish itself from the sibling election_voting_systems tool, so it falls short of full sibling differentiation.

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?

Gives clear usage constraints: missing/Other answers don't mean no equipment, the survey doesn't establish equipment on a specific date, and directs the agent to Verified Voting and the state election office for verification. It stops short of routing between this tool and the election_voting_systems sibling.

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