List downsells

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by the framework. The description contributes the account-wide scope and the downsell definition, but adds no detail about response shape or edge cases.

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 crisp sentences front-load the action and scope, then define the domain term and state practical uses. There is no repetition of schema or annotations and no unnecessary wording.

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 a one-optional-parameter read-only list tool with strong annotations, the description provides enough context to call it correctly. It could be slightly more explicit about what the returned list contains, but the stated goal of getting an id for get_downsell compensates.

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 account parameter is fully documented in the schema (default behavior, list_accounts, account isolation), so the description does not need to add parameter detail. The description's mention of 'a ThriveCart account' aligns with the schema but adds no new parameter semantics.

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 names a specific action ('List every downsell') and resource ('across all products on a ThriveCart account'), and defines downsell as the fallback offer after an upsell is declined. This clearly distinguishes it from siblings like list_upsells and list_products.

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 explicitly says to use this to explore offers beyond main products and to obtain an id for get_downsell. It does not explicitly contrast with list_upsells or list_bumps, but the use cases are clear enough for selection.

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