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

Annotations already declare readOnlyHint=true, so the safety bar is lower; the description still reinforces it with 'Changes nothing' and adds genuine behavioral value by disclosing the returned payload shape and the backing endpoint (POST /shipping/rates). It stops short of mentioning auth scope nuances or error behavior.

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 tight sentences: what it returns is front-loaded, the minimal required inputs follow, then the no-side-effect and endpoint notes. No filler.

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?

With no output schema, the description compensates by enumerating the response fields, and it covers the nested recipient requirements. Minor gaps remain around failure modes (invalid address, unsupported country) and rate-limit behavior, but the essentials for correct invocation are present.

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% (baseline 3), but the description adds a useful condensing rule the agent would otherwise have to assemble from nested schemas: only country_code is required, with state_code needed for US/CA/AU. That marginal clarification lifts it slightly above baseline.

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 (Quote), resource (shipping options), and even enumerates the returned fields (method id, name, rate, delivery-day estimate). It is clearly distinguishable from the other printful tools at a glance.

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 implies a pre-purchase quoting context and notes 'Changes nothing', but never says when to prefer this over the closest sibling, printful_estimate_order_costs, or any other alternative. Usage is inferable but not explicitly routed.

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