market_compare

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

No annotations provided, so the description must convey behavior. It mentions timeout avoidance with country/store, but does not disclose return format, pagination, error handling, or data freshness. Adequate but not thorough.

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 sentences, no waste. First sentence gives purpose and constraint (one query, side-by-side). Second sentence gives usage guidance and a practical hint. Front-loaded and efficient.

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 6 parameters and no output schema, more detail could be helpful. While schema covers parameters, the description omits what 'side-by-side' results look like (e.g., list, table) and doesn't explain line or TCO. Adequate for a basic tool but could be richer.

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 83%, so most parameters are described. The description adds context beyond schema, e.g., 'Set country (e.g. PE) or store to avoid timeouts,' which explains the performance implication. Provides examples and usage tips.

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 'Compare prices for one query across retailers side-by-side,' which is a specific verb+resource. It distinguishes from siblings like market_search and market_discover.

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?

Explicitly says 'Use when the user asks for cheapest option or cross-store comparison,' providing clear when-to-use guidance. Also hints at setting country or store to avoid timeouts, though no explicit when-not or alternatives.

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