getDeliveries

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that no arguments are required and lists the returned data fields (ID, name, fee rules, areas), further clarifying the tool's output and ensuring no contradiction.

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 four concise sentences, front-loaded with the main purpose. Every sentence adds relevant information (return fields, use cases, reference to sibling tool) without wasted 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?

For a read-only list tool without an output schema, the description adequately explains the returned fields and two common use cases. It does not mention pagination or rate limits, but the annotations (openWorldHint) and typical usage reduce the need for further detail.

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?

The input schema has a single dummy parameter with a clear 'Not used' description, achieving 100% coverage. The description explicitly states 'no arguments required', reinforcing that the parameter is irrelevant, which adds value beyond the schema.

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 it retrieves a list of valid shipping methods for the shop, specifying returned fields (ID, name, fee rules, areas). It distinguishes itself from the sibling tool getDeliveryDateSetting by directing users to that tool for delivery date/time settings.

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 provides two specific use cases (presenting options before order creation, matching delivery_id) and explicitly references the sibling tool getDeliveryDateSetting for date/time needs. It lacks explicit 'when not to use' guidance but the context is clear.

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