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

The description reinforces the readOnlyHint annotation by explicitly stating 'Non-destructive — it only prices, it does NOT place an order', and adds the REST endpoint. This goes beyond the annotation to prevent misuse.

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?

Three concise sentences plus the REST endpoint. Every sentence adds critical information without redundancy, making it easy to parse.

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?

The description covers purpose, parameter shapes, and non-destructive behavior, but does not describe the response format. Since there is no output schema, a brief note on the returned quote structure would complete it.

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 description provides substantial meaning for line_items (three accepted shapes) and address_to (full field list), far exceeding the minimal schema descriptions. Shop_id is clearly defined by 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 states a specific action: 'Get a shipping price quote' for line items to a destination. It clearly distinguishes from sibling list/get tools by focusing on shipping quotes and explicitly noting it does not place an order.

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 clear context on when to use this tool (for pricing) and explicitly states a non-ordering behavior. It lacks explicit alternatives, but given the sibling set has no direct ordering tool, the guidance is strong.

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