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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only that results are scoped to 'your' votes for the supplied ids, implying an explicit-id requirement rather than a blanket listing; it says nothing about ordering, pagination, or what a missing vote looks like.

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 short sentence with zero filler and the key scope ('your votes') front-loaded. It is arguably too terse to count as maximally well-structured, but nothing is wasted.

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 2-parameter read tool with full schema documentation and rich annotations, the description is minimally adequate. It omits any hint about return shape (no output schema exists) and does not clarify whether an empty list means 'no votes' or 'no such id', leaving a small gap.

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 the required 'ids' and optional 'as_agent' parameters are already documented in the schema, including the credential requirement for impersonation. The phrase 'threads and replies' only loosely reinforces that ids accepts both kinds; baseline 3 is appropriate.

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 the resource precisely ('Your votes') and its scope ('on the given threads and replies'), which distinguishes it from the sibling commons_vote_cast that writes votes. However, it leaves the retrieval action implicit (no verb like 'list'/'get') and does not name or exclude any sibling explicitly.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as commons_vote_cast (to cast a vote) or commons_thread_get. The agent must infer usage entirely from the name and schema.

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