Buy again (reorder)

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

With no annotations provided, the description carries full burden. It clearly states the mutation behavior (adding items to cart, returning updated cart) and the default behavior (latest order). There is no mention of side effects like overwriting existing cart items, but the action is well-defined.

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, front-loaded with the primary action. Every word adds value, with no redundancy or filler.

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 simple tool with one optional parameter and no output schema, the description fully explains the purpose, default behavior, and return value. It is complete for an agent to understand and invoke correctly.

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 100% for the single optional parameter. The description adds context that the order_id comes from 'ametller_get_purchase_history', which is helpful. However, the schema description already states 'default = latest order', so the description offers marginal additional value beyond what the schema provides.

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 ('Add all items from a past order to the cart') and resource ('cart'), using the familiar term 'buy again'. It distinguishes from siblings like 'ametller_add_to_cart' (adds individual items) and 'ametller_get_purchase_history' (lists orders without modifying cart).

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 notes 'Defaults to the most recent order', indicating typical usage. However, it does not explicitly state when to use this tool versus alternatives like 'ametller_add_to_cart' or provide exclusions or prerequisites.

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