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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds genuinely useful context: it names the underlying POST /shippingprices endpoint and pre-empts the natural misreading that a POST mutates state by stating 'nothing is ordered'. It also describes the return content (methods, price, delivery days), which matters since there is no output schema.

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 tight sentences with zero filler; the primary capability and its output shape come first, and the endpoint/side-effect clarification follows. Every clause 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 5-parameter, fully documented schema with no output schema, the description covers inputs, the nature of the operation, and the shape of the result. The remaining gap is sibling differentiation against gooten_get_shipping_estimate and gooten_get_price_estimate.

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 100%, so the schema already documents items, sku, quantity, country_code, postal_code, state, and currency_code in detail. The description only restates 'a cart of SKUs to a destination' without adding format, limits, or default information beyond what the schema provides; baseline 3 applies.

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+resource ('shipping options for a cart') and enumerates the concrete outputs (Standard/Expedited/Overnight, price, delivery days). It does not, however, distinguish itself from the close sibling gooten_get_shipping_estimate, which an agent could easily confuse it with.

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 parenthetical 'a quote: nothing is ordered' implies this is a pre-purchase check, but there is no explicit when-to-use or when-not guidance. With siblings like gooten_get_shipping_estimate, gooten_get_price_estimate, and gooten_validate_address in the list, the agent is left to infer the routing decision.

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