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

Annotations already confirm this is a safe read operation, so safety burden is lifted. The description adds useful context about the output format (Markdown in Brazilian Portuguese), which isn't in annotations, but doesn't cover latency, caching, or freshness of data.

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 a single, dense sentence that front-loads the return contents and tacks on format information. No waste.

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?

An output schema exists, so return values needn't be explained. For a read-only tool with one well-documented parameter, the description is adequate but doesn't mention any dependencies, error conditions, or when to prefer this over siblings. It's minimally complete.

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?

With a single parameter and 100% schema coverage, the schema fully documents the 'id' parameter. The description adds no further parameter meaning, so the 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 provides a specific inventory of what the tool returns (current offers, lowest price, stats, reviews, specs), making the tool's purpose clear. However, it doesn't distinguish itself from siblings like get_price_history or check_product_url, so sibling differentiation is absent.

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?

No explicit guidance on when to use this tool versus alternatives. The description lacks exclusions or routing to siblings, leaving usage to inference.

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