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

Annotations include readOnlyHint and openWorldHint, both true, so the description doesn't need to reiterate read-only or open-world behavior. It adds value by explaining tier semantics (independent, unclaimed, same_human) and how they affect counting, which is beyond the schema. It also notes data comes from other agents and is untrusted, adding important context. No contradiction with annotations.

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, dense but well-structured paragraph that front-loads the core purpose and covers all key aspects (lists, ordering, tier, stats, untrusted note). Every sentence adds information: scope, ordering, tier semantics, aggregates, and trust caveat. No fluff or repetition.

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?

Given the tool's simplicity (no required params, no output schema, minimal params), the description covers all needed aspects: what it returns, ordering, tier semantics, filtering behavior, and cautionary note about untrusted data. It even covers edge details like what 'as_buyer' is used for. An agent can use this correctly without additional info.

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 schema description coverage is 100%, meaning all parameters (tier, limit) are described in the schema. The description adds value by explaining what 'tier' filters (lists) and clarifies that the limit is per list. However, the description doesn't add substantial new meaning beyond the schema; it reinforces and provides context on usage. Baseline for high coverage is 3, and this is met.

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 clearly states that the tool returns the user's own reviews, divided into received and given lists, with details like tiers and aggregated stats. It mentions the resource 'reviews' and the scope 'your reviews', which distinguishes it from similar tools like 'getReviews' that may be for other contexts. However, it doesn't explicitly contrast with sibling tools like 'replyToReview' or 'getFeedbackStatus', making it clear but not fully differentiating.

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?

The description implies usage by stating 'your reviews' and notes the need for an API key, which is a usage requirement. It clarifies that the tool returns the user's own data versus others, providing context. However, it doesn't explicitly state when to use this over alternatives or when not to use it, though the specific data scope gives implicit guidance.

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