Store order options

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

No annotations are provided, so the description carries the full burden. It clearly labels the operation as read-only by using 'Read' and stating 'No checkout or order placement'. It lists the data returned but does not disclose permissions, rate limits, or side effects, though for a read-only tool this is minimally acceptable.

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 sentences long, front-loads the key purpose, and contains no redundant 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?

With four parameters, no output schema, and no annotations, the description provides a high-level understanding but lacks guidance on how to use specific parameters (e.g., translation language, similar_limit). It is minimally complete for an agent to infer behavior but leaves gaps.

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 50% (only 'translation' and 'similar_limit' have schema descriptions). The tool description does not add any parameter-specific information beyond the schema, failing to compensate for the missing schema descriptions of 'store_id' and 'store_address_id'.

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 verb 'Read' and the resource 'store order options', listing specific elements like delivery minimums, surcharges, restrictions, public store info, and similar stores. It also distinguishes itself from siblings by noting it is a pre-basket read operation, not checkout or order placement.

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?

The description explicitly states 'before preparing a basket' (when to use) and 'No checkout or order placement' (when not to use). However, it does not name specific alternative tools for comparison, but the context is clear enough for an agent to decide.

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