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

'Changes nothing' and the endpoint reference 'Printful: POST /shipping/rates' are useful, especially since a POST verb might otherwise suggest a mutation and the note reconciles it with readOnlyHint. Beyond that reconciliation, no additional behavioral context is given (no auth/permission notes, rate limits, or failure modes), so this only slightly exceeds what the annotation already declares.

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 with zero filler: purpose and output shape first, then the minimal input requirement, then the side-effect statement and endpoint. Front-loaded and appropriately sized for the tool's complexity.

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?

There is no output schema, but the description compensates by naming the return fields (method id, name, rate, delivery-day estimate). Combined with 100% schema coverage for the nested recipient/items objects, an agent has enough to call the tool correctly; a note on error/empty-rate behavior would be the only missing piece.

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 mention of country_code being the only required field and state_code for US/CA/AU duplicates what the schema already states verbatim ('Required for US, CA and AU'), adding no semantics beyond the structured data.

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') and resource ('shipping options') and even enumerates the returned fields (method id, name, rate, delivery-day estimate), so the agent knows exactly what comes back. It does not explicitly distinguish itself from the sibling printful_estimate_order_costs, which is the nearest lookalike, keeping it short of a 5.

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 requirement 'Only country_code is required (plus state_code for US/CA/AU)' tells the agent what input is minimally needed, implying when the call is usable. However, there is no explicit when-to-use vs. when-not guidance and no routing to an alternative such as printful_estimate_order_costs, leaving the agent to infer the boundary.

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