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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds substantial behavioral context by detailing the returned fields (templateId, orientation, previewUrls, etc.) and explaining their semantics, plus the field-level attributes and workflow requirements. It does not contradict annotations but also doesn't mention error cases or limitations, which are minor for a read-only list tool.

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?

The description is lengthy but well-structured: it opens with purpose, enumerates output fields, explains each field type, and then gives a clear workflow. It is front-loaded and every sentence adds value, though it could be trimmed slightly without losing meaning. The organization compensates for its length.

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?

Given the absence of an output schema, the description thoroughly explains the return values and their semantics, including field attributes, input types, requiredness, and sample values. It also ties into the surrounding toolchain (get_product, create_business_card_design, get_quote, create_checkout), making it complete for an agent to use correctly.

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 tool takes zero parameters, so the baseline of 4 applies. The description adds no parameter-specific details because there are none, which is appropriate.

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 explicitly states it lists business card templates and positions it as the entry point for the design workflow ('Start here to design a business card'). It clearly distinguishes itself from siblings by describing its output (template details) and the downstream steps, making its role 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?

It provides explicit guidance on when to use this tool (as the first step) and how to proceed: checking productHandle with get_product, then calling create_business_card_design, get_quote, and create_checkout. It also notes it takes no arguments, leaving no ambiguity about invocation.

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