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

Annotations indicate read-only, idempotent, non-destructive behavior. The description adds crucial behavioral details (robots.txt compliance, no JavaScript, no anti-bot bypass) and specifies the exact output structure, going well beyond the 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 long due to listing output fields, but every sentence adds value and it is front-loaded with purpose. It is efficient with no fluff, though slightly verbose.

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 a rich output schema and clear annotations, the description fully explains the tool's behavior, constraints, and parameter usage, making it complete for this moderately complex web-fetching 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 coverage is 67%; the description clarifies the optional comparison via 'optionally compare the selected offer with a buyer-supplied maximum' for maximum_price, but does not mention expected_currency beyond its schema description. Baseline 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 states a specific action ('Paste one public retailer product URL to get its current publisher-supplied structured price') with a clear resource and enumerates the exact data fields returned, distinguishing it from sibling tools focused on other domains.

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?

It clearly states when the tool works ('Fetching proceeds only when robots.txt permits it') and its constraints (no JavaScript, login, etc.), implying appropriate usage contexts. It does not explicitly name alternative tools, but its domain is distinct.

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