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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description adds real context on top of that: results are sorted newest first and the concrete field set (status values, schedule, voters, ballots, links) that an agent will receive.

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?

A single sentence with a front-loaded resource and scope, followed by a colon list of returned fields; nothing is padded. The trailing 'links to hand the person' is slightly colloquial but still economical and informative.

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?

There is no output schema, so the description usefully compensates by enumerating the return shape (id, slug, title, kind, status, schedule, voters, ballots, links). For a read-only list tool with two optional, fully-documented parameters, this is close to complete; only ordering/pagination caveats are left implicit.

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 limit (default 20, max 50) and status (default all, enum values) are already fully documented in the schema. The description restates the status vocabulary and implies ordering but adds no filtering or pagination semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb (implicit list) and resource (elections and surveys) scoped to 'the connected vote.direct account', and enumerates the returned fields, so the agent knows exactly what comes back. It does not explicitly distinguish itself from get_election (singular) or the create/publish siblings, which keeps it short of 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?

Usage is only implied: the tool is for browsing the account's elections/surveys, with defaults for limit and status mentioned only via the schema. There is no statement of when to prefer this over get_election or get_governance_center_overview, nor any exclusion for archived or other-account resources.

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