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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the bar for added context is lower. The description usefully discloses the payload shape (member-level yes/no/other/absent records) and that bill_id returns all recorded votes, but says nothing about ordering, pagination, or behavior when neither id is supplied.

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, zero filler, and the resource scope is front-loaded before the parameter routing. 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 partially compensates by characterizing the returned records at member level. Annotations cover the safety profile, so the only real omission is the no-argument/both-argument default behavior for a tool where zero parameters are required.

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% and both parameters are optional with no descriptions, so the description carries the full burden. It does define both: vote_event_id selects a single vote event, bill_id returns all recorded votes for a bill. It does not state what happens if both are omitted or supplied together, which is the remaining gap.

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 verb and resource ('Fetch vote event(s)') and immediately narrows the payload to 'member-level (yes/no/other/absent) vote records'. No sibling tool covers vote events, so the agent can distinguish this from get_bill_record or trace_legislative_history without opening a schema.

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?

'Provide vote_event_id for one vote, or bill_id for all recorded votes on that bill' gives clear invocation modes, but this is really parameter routing rather than when-to-use guidance. It names no alternative tool, no exclusion condition, and no case where a different sibling (e.g. get_bill_record) would be preferred.

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