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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds value beyond that by confirming it only prices and does not mutate state, and by disclosing the underlying REST call. It does not describe return shape, pagination, or failure modes (e.g., unpriced/unshippable items).

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?

Front-loaded with purpose and the most consequential caveat, then two dense but efficient parameter sentences. The trailing REST endpoint line is compact and useful for API-aware agents, though the inline brace-list notation reads a bit like spec text.

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?

Covers all three required params and their nested shapes thoroughly despite the permissive schema. With no output schema, the quote's return structure is left undescribed, which is the one gap for a pricing tool whose output is the whole point.

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 baseline would be 3, but the raw schema for address_to and line_items is only `additionalProperties: {}` with no field names. The description compensates by enumerating all three accepted line-item shapes and the full address_to field set, which is information the schema genuinely lacks.

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 ('Get a shipping price quote') with clear scope ('for a set of line items to a destination address'). It explicitly distinguishes itself from order-placement tools via 'it does NOT place an order', which separates it from printify_list_orders/printify_get_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?

Clear context: use this to price before ordering, and the 'does NOT place an order' clause tells the agent when not to use it. However, it does not name a sibling alternative for the actual ordering step, leaving the routing half-implicit.

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