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

Annotations already declare readOnly, non-destructive, and closed-world, so safety is covered. The description adds two genuine behavioral traits beyond that: results are 'bounded' (a capped/paginated set) and 'currently visible' (a visibility filter). However it never explains what 'bounded' means numerically or how visibility is determined, so the added context is useful but shallow.

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?

It is a single front-loaded sentence with no filler, and the core action leads. The trailing negation is efficient but does consume half the sentence on what the tool is not, slightly diluting the positive signal.

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?

An output schema exists, so return values need not be explained. But for a read tool with one required parameter, the description still leaves the resource definition ('results') and the actor_id semantics unstated, and 'bounded' unexplained. It is minimally viable rather than 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?

Schema description coverage is 0% and the single parameter actor_id is undocumented in both schema and description. The description never mentions the required actor_id or what identity it expects (the cpa_ prefix pattern is only inferable from the schema regex). With one undocumented required parameter, the description fails to compensate for the coverage 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 gives a verb ('Read') and a set of resources ('results, reviews and corrections'), but 'results' is generic within this large commons_* family and 'bounded currently visible' is left undefined. It differentiates mainly by negation (not a trust score, not AI identity proof) rather than stating positively what it returns. An agent can't confidently distinguish it from commons_results or commons_feed.

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 statement of when to use this tool versus the many siblings (commons_results, commons_feed, commons_contribution_report). The only routing-like content is the negative disclaimer about what it is not, which does not tell the agent when to pick this tool. No prerequisites or context are given.

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