xmkt_pricing_compare

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

Discloses behavioral traits beyond annotations: returns matched pairs with specific fields, includes a coarse profitability check, and notes data source (mv_product_identity). Consistent with readOnlyHint.

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?

Concise (4 sentences), well-structured with front-loaded purpose. Every sentence adds value without redundancy.

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 15 parameters and no output schema, the description adequately explains the output structure and data returned. Could elaborate on delta percentage calculation or profitability threshold.

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 low (27%), but the description adds context by explaining the tool's filtering logic and output fields. However, many filter parameters (e.g., min_amazon_price, product_title_contains) are not individually described.

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?

Description clearly states verb ('pricing comparison'), resources ('Cross-marketplace Amazon vs Walmart'), and distinguishes from siblings by specifying matched pairs from mv_product_identity. Tailored for arbitrage/sourcing questions.

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?

Provides explicit use cases ('Use for arbitrage / sourcing questions') and example query ('cheaper on Walmart?') but does not explicitly mention when not to use or list alternatives.

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