compare_prices

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the basic action and does not explain what the comparison involves, how results are ordered, what data is returned, or any side effects. This is a significant gap for a tool with no output schema.

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 short sentence with no padding, front-loaded with the verb. It is concise and efficiently stated, though slightly too terse to fully capture the tool's purpose. Given the schema covers parameters, the minimalism is acceptable.

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?

The tool has no output schema and only a two-word description. It lacks details on return structure, the meaning of 'comparing prices' (e.g., across stores, sorted by distance?), and any context relative to similar tools. For a tool with moderate complexity, this is incomplete.

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 input schema provides 100% coverage with descriptive parameter descriptions (productId, latitude, longitude). The tool description adds no additional semantic value beyond the schema, so the 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 clearly states the action ('compares') and resource ('product prices'), making the basic purpose evident. However, it does not distinguish itself from sibling tools like 'compare_markets' or 'find_cheapest', and the role of latitude/longitude in the comparison is not implied.

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?

There is no guidance on when to use this tool versus alternatives. The description only states the action, with no mention of preferred scenarios, prerequisites, or exclusions. Users are left to infer usage from the parameter names, which is insufficient.

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