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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is carried by structured data. The description adds only the HTTP endpoint mapping; it says nothing about result ordering, page sizes beyond the schema, or whether disabled methods are included.

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, front-loaded with the resource and its scope. The endpoint reference is compact and useful for agents mapping to the API surface; nothing is padded or redundant.

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 two-param read tool with full annotation coverage this is close to sufficient, but there is no output schema, so a brief note on what a shipping method record contains (name, rate, zones) would have made the definition self-contained.

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% and both params (page, limit) are fully documented in the schema, including ranges, defaults and the next_page chaining hint. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ('List the store's shipping methods and rates') plus the underlying endpoint (GET /v1/shippings), so the agent knows exactly what data comes back. It does not explicitly contrast with near-neighbours like list_payment_methods or list_zones, but the resource is unambiguous enough that confusion is unlikely.

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?

Usage is only implied: it is evidently the read path for shipping configuration, and the readOnly annotation reinforces that. There is no explicit when-to-use, no mention of alternatives (list_zones, list_payment_methods) and no note on when pagination is needed.

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