List products

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds scoping context by emphasizing 'every product' and the fact that ids and names are returned, which is useful beyond the annotations, but it does not disclose additional behavioral traits such as pagination or ordering.

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 two sentences with no filler. The first sentence states the core function and output fields; the second sentence gives practical usage guidance. Every word contributes value.

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 simple, read-only listing tool with no output schema, the description plus the fully documented parameter and rich annotations provide everything an agent needs to select and invoke it correctly. The return shape is stated ('ids and names'), and the account scoping is covered by the schema.

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 description coverage is 100%: the single 'account' parameter is fully documented in the input schema, including its default behavior and relationship to list_accounts. The tool description adds no parameter-specific meaning, so the baseline of 3 applies because the schema carries the explanatory burden.

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 uses a specific verb and resource: 'List every product on a ThriveCart account, with ids and names.' It clearly distinguishes this from sibling list tools like list_bumps, list_upsells, and list_downsells by focusing on products, and the 'Start here when you need a product id' phrasing reinforces its entry-point role.

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 provides clear context for when to use the tool: 'Start here when you need a product id for another tool, or to see what a cart actually sells.' It does not explicitly name an alternative to avoid or state when not to use it, so it stops short of a 5, but the guidance is unambiguous.

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