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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful scope and behavior: it reads only public records, excludes private participants and conversations, and instructs preservation of citations, methodology, coverage, and dates. It does not cover pagination or rate limits, but with annotations present this is a solid addition.

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 tightly written sentences with the purpose front-loaded, followed by preservation expectations and exclusions. Every sentence adds distinct information with no filler.

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?

The tool has 7 parameters, multiple large enums, 0% schema description coverage, and no output schema. The description covers high-level intent and exclusions but leaves the agent without guidance on how to populate most parameters or interpret return content, making it incomplete for this complexity.

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 0%, so the description must carry parameter meaning, but it only loosely references 'collections' and 'a catalog chart' and 'dates'. It does not explain the required resource enum, the many chart values, or parameters such as query, state, office, and district.

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 uses a specific verb ('Read') and identifies the resource scope as public Election.org collections or a catalog chart. It does not explicitly distinguish this tool from the sibling tools read_public_catalog and read_public_indicator, which keeps it from a 5.

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 exclusion statement ('Does not read private participants, political profiles or user conversations') gives useful when-not guidance. However, it does not say when to choose this tool over read_public_catalog or read_public_indicator, so usage guidance is only implied.

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