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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses data sources ('observed catalogue prices and published delivery rules'), handling of unknowns ('unknown delivery stays unknown'), explicit matching proposals for product and quantity, and ranking/minimum-order behavior. This is rich behavioral context that an agent cannot get from structured fields alone.

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?

Four tightly written sentences, front-loaded with the core purpose, and each subsequent sentence adds behavioral detail without filler. No wasted words.

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?

For a read-only, open-world tool with an output schema, the behavioral context is strong enough. However, the complete absence of parameter-level guidance given 0% schema coverage is a notable gap that leaves the agent guessing about how to populate 'items' and what 'area' does.

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 description coverage is 0% and there are 2 parameters, so the description must compensate. It only indirectly implies that 'items' is the grocery list and 'area' relates to Dubai location; it never explains the area parameter, the item string format (e.g., product names, quantities), or constraints, leaving most parameter semantics undocumented.

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 verb ('Compare'), resource ('total cost of a grocery list'), and scope ('across Dubai supermarkets'). It also clarifies single-product ranking and minimum-order behavior, which distinguishes it from siblings like find_price_online (single product) and list_stores.

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?

Usage is implied by 'Compare the total cost of a grocery list across Dubai supermarkets' and the note about single-product ranking, but there is no explicit when-to-use guidance, no exclusions, and no named alternatives such as find_price_online for single-product lookups.

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