getReviews

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

Annotations already mark it as read-only, non-destructive, idempotent, and open-world. Description adds behavioral context: returns all non-deleted reviews irrespective of approval status. No contradictions 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?

Single paragraph with all essential information, front-loaded with purpose. Could be slightly more structured (e.g., listing fields), but no unnecessary words.

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?

No output schema, but description lists key fields returned. Covers pagination and status behavior. Missing sorting order (e.g., by posted_at) and authentication requirements, but given the simple nature, it's fairly complete for a 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 covers both parameters with descriptions. Description reinforces pagination and adds context: max limit 100, default 10, offset meaning. Adds value beyond schema.

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?

Description clearly states it retrieves a list of product reviews for a shop, specifies included fields (nickname, product_id, star, etc.), and distinguishes from getProduct by referencing it for product details.

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?

Provides pagination details (limit/offset, max 100, default 10) and mentions that all non-deleted reviews are returned regardless of approval status. References getProduct for product details, but does not explicitly state when to use this tool versus alternatives like getProducts.

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