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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds useful behavioral context by disclosing the evidence basis (votes, sponsorship, statements, or self-reported to The Wiley Rule) and constraining the output to name, office, district, party and an evidence label.

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?

Two sentences, front-loaded with the definition and then the returned fields; no filler. Slightly dense with parenthetical sourcing detail but every clause earns its place.

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 correctly spells out the returned fields. It does not explain what the 'evidence label' values mean, but for a simple filtered lookup with full annotation coverage it is nearly complete.

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?

There is a single optional 'office' filter and schema description coverage is 100%, so the baseline is 3. The description never mentions the filter or its accepted values, so it adds nothing beyond the schema.

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 states a specific resource and inclusion criterion: officials with a public record of supporting action on 7-OH. It is a listing/lookup tool, but it does not differentiate itself from siblings such as state_actions or find_my_lawmakers, so the boundary is left to inference.

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 explicit when-to-use or when-not-to-use guidance, and no sibling alternative is named despite there being several overlapping tools (state_actions, find_my_lawmakers, nc_legislation). The inclusion criteria hint at scope but do not route the agent among alternatives.

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