list_shipping_zone_methods

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

Annotations already declare readOnlyHint=true, so the description need not restate safety. It adds domain context (what methods are) but does not disclose behavioral details like return format, pagination, or the effect of the 'fields' parameter. This is acceptable given the simple read-only nature, but no extra behavioral traits are revealed 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?

Two short sentences with no filler. The first sentence states the purpose directly, and the second provides useful 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?

For a simple list tool with good annotations and full schema coverage, the description is adequate. It doesn't explain return structure, but the rules say output schema isn't required for that. It could mention the 'fields' parameter's purpose, but the schema covers it. Overall sufficient for an agent to select and invoke correctly.

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 description coverage is 100%, so the baseline is 3. The description complements the schema by explaining that methods define shipping options, but it does not add syntax or format details beyond what the schema already provides. The examples of method types are helpful but not parameter-specific.

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 uses a specific verb ('List') and resource ('shipping methods') with a clear scope ('for a zone'). It also provides examples (flat rate, free shipping, local pickup) that distinguish this tool from siblings like list_shipping_zones or add_shipping_zone_method.

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 clearly implies when to use this tool: whenever you need to see shipping methods for a specific zone. Although it doesn't explicitly state alternatives or exclusions, there is no sibling tool that performs a similar list operation, so the context is sufficient. A slightly more explicit 'use this to...' could push it to 5.

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