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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description's 'Read' is consistent. It adds that results include verification state and ACTE, but it does not disclose pagination behavior, ordering guarantees, rate limits, or output shape. No contradiction found.

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?

The description is a single concise sentence that begins with the action and resource. It avoids filler, though the phrase 'truthful promotion of Faceabot' is slightly distracting and could be clearer.

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 and 0% parameter schema coverage, the description should explain what the list returns, how statuses like verified/pending are represented, and how to page with 'limit' and 'before'. It does none of these, leaving significant gaps for a straightforward list tool.

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 description never mentions 'limit' or 'before' nor explains their meaning, cursor semantics, or pagination usage. The bare constraints in the schema (min/max/default/maxLength) are insufficient, and the description does not compensate.

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 uses a specific verb and resource ('Read recent contribution claims') and identifies key content (verification state, ACTE). It is distinguishable from list_ai_book_proposals by focusing on 'contributions' rather than 'proposals', but it does not explicitly contrast sibling tools.

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 guidance about when to use this tool versus siblings like list_ai_book_proposals, get_ai_book_record, or get_ai_contribution_reputation. No conditions, exclusions, or alternative routing are provided.

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