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

Annotations cover the safety profile (not read-only, open-world, non-destructive), and the description adds real behavioral context beyond them: the coupon is enabled immediately, max_uses aggregates across customers, fixed coupons apply once to main product only, and there is a per-call confirmation workflow plus an API key requirement. Some of this overlaps schema param text but the workflow and lifecycle details are net-new.

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?

Purpose is front-loaded and most sentences carry information, but several restate schema param descriptions (code character rule, max_uses) and the confirmation/API-key tail is slightly run-on. Dense but not wasteful.

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?

For an 11-parameter mutation tool with full schema coverage and no output schema, the description covers lifecycle, scoping, confirmation, and auth prerequisites adequately. Only the absence of explicit sibling routing keeps it short of complete.

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 is 3. The description exceeds that by explaining the logic behind applies_to (percentage can target funnel/bumps; fixed is main-product-only-and-once) and clarifying that max_uses is a total, not per-customer — semantics the raw enum/integer fields do not convey.

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 (creates) and resource (coupon) and immediately scopes what the coupon contains (fixed or percentage discount, dates, use limit, products). An agent can distinguish this from thrivecart_list_coupons and thrivecart_update_coupon without opening schemas.

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?

Provides substantial context about constraints (code format, when each discount type applies, enabled-on-create) but never explicitly states when to choose this tool over siblings like update_coupon or how it relates to list_coupons. Usage is implied rather than routed.

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