Plan a repeat order

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

With no annotations, the description carries the full burden. It clearly states the tool is read-only and that users should inspect product options and obtain approval before using basket tools. This disclosure of non-destructive behavior is valuable, though more detail on return format or auth needs would strengthen it.

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 with no filler. The first sentence conveys the core action, and the second provides usage context. Every word 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?

Given the tool has no output schema and three parameters, the description is minimal. It lacks details on what the output looks like or how to interpret results (e.g., which products are unavailable). For a reorder planning tool, more context on the resolution process would improve completeness.

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%, so baseline is 3. The description adds no parameter-level information beyond the schema; it does not explain what max_searches or candidates_per_line control in relation to the planning process. This is adequate but not enhanced.

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 resolves past order lines against current store results for planning a repeat order. This distinguishes it from general basket tools and suggests a planning role, though the difference from glovo_preview_reorder is not explicit.

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 implies this tool is a read-only planning step before using basket tools, but does not explicitly state when to use it over similar tools like glovo_preview_reorder or glovo_add_to_basket. More concrete when-to-use and when-not-to-use guidance would help.

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