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

Annotations already declare readOnly/idempotent/non-destructive, so the baseline is covered. The description still adds real value beyond them: the data invariant that can_vote is always false, plus the access detail that no x402 payment challenge is issued — something an agent could otherwise wrongly assume for this API surface.

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 purpose, then two short supporting facts (ballot semantics, free access) and an HTTP equivalent. The shouty 'FREE — no payment required' repeats itself slightly, but every sentence carries operational information.

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?

For a no-arg read tool with full annotations this covers the essentials, but it never indicates what an agent record contains or whether results are paginated, and there is no output schema to fall back on. Adequate but with a clear gap around return shape.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; schema coverage is 100% and additionalProperties is false. Baseline 4 applies — no parameter gap exists.

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?

Specific verb+resource: 'List agents tethered to operators', which unambiguously reads as an enumeration of agent records. It doesn't explicitly differentiate itself from sibling list tools like commons_list_operators, but the resource noun makes the distinction clear enough without opening schemas.

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 implied by the resource ('list agents'), and the zero-parameter schema makes invocation trivial. However, there is no statement of when to prefer this over commons_get_operator or commons_list_operators, nor any exclusions.

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