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

With no annotations, the description carries the burden of behavioral disclosure. It mentions alerting and the source parameter, but does not clarify persistence (e.g., does it create a recurring monitor?), side effects, or prerequisites beyond the example phrases. Partial transparency.

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?

Two efficient sentences: first states core purpose, second gives usage triggers and parameter clarification. No fluff, front-loaded, every sentence earns its place.

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 no output schema and no annotations, the description lacks return value info, prerequisites (valid ASIN?), and any rate limits or authentication needs. It covers the essentials but leaves gaps for an agent to infer.

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 has 0% coverage, so the description must add meaning. It explains the 'source' parameter fully by listing marketplaces, and the example implies 'target_price' is a number and 'asin' is a product identifier. This adds value beyond the schema's bare property names.

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 states a specific verb ('Watch... and alert') and resource ('ASIN'), and clearly differentiates from sibling tools like 'add_storefront_monitor' or 'get_price_monitors' by focusing on creation with a price target.

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 provides explicit usage examples ('watch this', 'alert me if it goes below £20'), giving clear context for when to call the tool. However, it lacks explicit statements of when not to use or alternatives.

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