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

Annotations (readOnlyHint=false, destructiveHint=false) are consistent with the mutating action of adding to cart. The description adds the checkout flow context and the prerequisite that print_id is finished, which are useful behavioral details beyond the 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 sentences: first states purpose, second lists arguments with concise parenthetical hints. No fluff. Every word earns its place, and the structure is front-loaded with the core action.

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 the main workflow: dependency on studio_status and integration with checkout flow. For a tool with moderate complexity (4 params, 2 required, plus output schema), it provides sufficient context to use correctly, though it could briefly mention error handling for invalid print_id.

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?

With 100% schema coverage, the description still adds value: it explains print_id must be done (linking to studio_status), product belongs to the same set as studio_generate, and size must be available for the chosen product. This contextual enrichment goes beyond the schema's basic descriptions.

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 clearly states the action ('Put a FINISHED custom print into the cart') and distinguishes from siblings like add_to_cart (presumably for existing products) and studio_generate (which creates prints). The verb 'put' and resource 'finished custom print' are specific and unambiguous.

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 gives context: 'print_id (must be done)' ties to studio_status, and 'Then the normal checkout flow applies (get_order_preview -> prepare_order)' explains downstream usage. It does not explicitly list when not to use the tool or alternatives, but the sibling context and parameter hints provide reasonable guidance.

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