Preview reorder

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

Explicitly states no mutation ('never mutates the basket or places an order'), which is critical for safe usage. With no annotations, description carries full burden and does well.

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?

Two sentences, no fluff, front-loaded with key purpose. Efficient and clear.

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?

Lacks return format details (e.g., boolean or status), but for a read-only preview tool, the description provides sufficient context for safe usage despite no output schema.

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 for order_id already indicates source (glovo_get_purchase_history). Description adds 'past order' context but limited extra value; schema coverage is 100%.

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?

Clearly states verb ('Read'), resource ('one past order'), and outcome ('report whether it can be safely rebuilt into a basket'). Distinguishes from mutation tools by emphasizing it never mutates.

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?

Implicitly suggests when to use (to check rebuild feasibility) but lacks explicit exclusions or references to sibling tools like glovo_add_to_basket for actual reordering.

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