list_reviews

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

No annotations are provided, so the description bears the full burden. It states a read-only operation ('List') but does not disclose any behavioral traits such as rate limits, idempotency, or potential side effects. The description adds minimal transparency beyond the obvious.

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 consists of two concise sentences, front-loading the purpose and adding a key requirement. Every sentence earns its place with no wasted verbiage.

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 complexity (3 optional parameters, no output schema), the description covers the core use case and a prerequisite. However, it omits pagination details (limit/offset behavior) and what the response format looks like, leaving some gaps for an agent.

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 schema already documents all parameters. The description adds the fact that filtering by 'status' is possible, which aligns with the schema. However, it does not add new meaning beyond what the schema already provides for 'limit' and 'offset'. Baseline of 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 clearly states the verb 'List' and the resource 'product reviews in your Karrito store', distinguishing it from sibling tools like 'list_my_products' and 'list_my_orders'. It also mentions filtering by moderation status, adding specificity.

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 includes a prerequisite (KARRITO_API_KEY) but provides no guidance on when to use this tool versus alternatives like 'moderate_review' or 'delete_review'. Usage context is implied but not explicitly stated.

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