find_best_store_for_item

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions sorting, limit, country filter, and storeIds precedence, but omits behavior regarding minQuantity, zero-stock stores, and no-match scenarios. This leaves significant gaps for a tool with no annotations.

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 two concise sentences that front-load the core purpose and sorting behavior, then add filter and precedence details. No redundant or wasted words; every sentence earns its place.

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?

No output schema or annotations exist, so the description must explain return values and edge cases. It provides a high-level return format but lacks detail on actual fields, error handling, and how minQuantity influences results. The tool has moderate complexity, so the description is adequate but not 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 0% schema description coverage, the description adds meaning to maxResults, countryCode, and storeIds (including precedence), but fails to mention itemNo (the required param) and minQuantity. It partially compensates but does not fully document all parameters.

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 tool's purpose: find stores with the highest in-stock quantity for a single item. It distinguishes itself from siblings like check_store_stock or find_best_store_for_cart by specifying the item-level search and the sorting by quantity descending.

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 the name and description, but there is no explicit guidance on when to choose this over alternatives like compare_store_stock or check_multi_item_stock. It does provide contextual info about optional filters and precedence, but no direct exclusions or comparisons.

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