watchlist_add_rule

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

Annotations declare readOnlyHint=true, consistent with the tool's read-only nature. The description adds behavioral details: it returns matching ASINs with scores, product identity, and fulfillment info. No mention of limitations or side effects, but annotations cover safety.

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 concise at two sentences and front-loads the primary purpose. However, it could be more structured to list behavior and output clearly.

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 19 parameters, no output schema, and only 26% parameter description coverage, the description is insufficient. It does not explain how natural-language resolution works, how filtering applies, or the full return structure.

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 only 26%. The description does not explain the numerous filter parameters (limit, min_composite_score, etc.) beyond mentioning brand and asin. Users lack guidance on how to use many parameters effectively.

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 tool's purpose: resolving natural-language watchlist requests into concrete ASINs. It provides specific examples ('watch this brand', 'alert me when X loses a seller') and distinguishes it from sibling watchlist tools that handle direct addition or removal.

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 explicitly tells when to use this tool ('Use when the user says... any watchlist-creation intent'). It offers clear context for usage but does not mention when not to use it or suggest alternatives like watchlist_add for direct ASIN additions.

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