⚠️ Orders: click-and-collect (details)

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

Annotations already indicate destructiveHint=false and readOnlyHint=false, so the 'Write operation' label is consistent but adds minimal new behavioral insight. The description does detail what fields are modified (address, booking period, comment) and mentions the dryRun parameter's safe preview, providing some additional transparency beyond 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 concise, with each sentence serving a clear purpose: purpose, nature, usage condition, and follow-up. No unnecessary words.

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's complexity (7 parameters, 3 required) and lack of output schema, the description covers essential workflow context (what it does, when to call, next step). It could be slightly improved by mentioning expected return or error conditions, but overall it's sufficiently 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 100% schema description coverage, the schema already documents each parameter adequately. The description briefly lists the key parameters (address, booking period, comment) but adds no new semantics beyond what's in the schema. Baseline 3 is appropriate.

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 'prepares a click-and-collect order and sends details to the buyer', specifying the action verb and resource. It also distinguishes itself from the sibling tool orders_apply_transition by noting the latter is used for confirmation after handover.

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?

Explicitly says 'Call it when the order has an available setCNCDetails action', providing clear when-to-use guidance. It also references the follow-up action orders_apply_transition, giving workflow context. However, it doesn't explicitly state when not to use or list alternative tools.

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