list_delivery_options

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

No annotations are provided, so the description carries the full burden. It specifies the API endpoint and return structure but does not disclose pagination, rate limits, or whether the list is filtered by 'enabled' or includes all options with a flag. Ambiguity exists between the phrase 'enabled delivery options' and the inclusion of an 'enabled' field.

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 well-structured with headings and bullet-style formatting. It is concise but includes useful details. Minor redundancy in listing examples could be trimmed, but overall it is efficient.

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 no output schema, the description provides the return structure with fields. However, it lacks information on pagination, sorting, and whether the list is truncated. For a list operation, this is a notable gap.

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 tool has no parameters, so the input schema is fully covered. The description does not need to add parameter information, and it appropriately omits any.

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 lists enabled delivery options for a store, with examples like home delivery, convenience store pickup, and in-store pickup. This distinguishes it from sibling tools like get_delivery_option_detail.

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 explains when to use this tool: to view all shipping methods and analyze delivery preferences. It does not explicitly state when not to use it or provide alternatives, but the context is clear given sibling tools.

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