select_delivery_interval

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

Annotations already provide idempotentHint=true and destructiveHint=true. The description adds the clarification that it does not place an order, which is consistent. However, it does not elaborate on what state change occurs (e.g., saving selection) or any side effects, leaving room for ambiguity.

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, front-loaded with the core action and key options. No unnecessary words. Every sentence adds value.

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?

The tool has an output schema and two parameters, but the description omits any mention of the output, fails to explain that 'interval_uuid' is required when 'delivery_type' is 'INTERVAL', and does not reference the sibling tool 'list_delivery_intervals'. Context is insufficient for an agent to use the tool correctly without prior knowledge.

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 0%, so the description must compensate. It names the enum values for 'delivery_type' but does not explain the 'interval_uuid' parameter at all. The relationship between 'INTERVAL' and 'interval_uuid' is not clarified, which is a significant gap.

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 that the tool selects among 'EXPRESS', 'SUPERFAST', or a listed 'INTERVAL', and explicitly notes that it does not place an order. This distinguishes it from ordering tools like 'confirm_order' or 'checkout_preview'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., after listing intervals with 'list_delivery_intervals', or prerequisites like having a store set). The tool's purpose is clear but context for usage is absent.

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