listProducts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the operation is read-only, indicates a GET endpoint, and discloses the rate limit (100 requests per 1m). This adds meaningful behavioral context beyond a simple 'list' statement.

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 a single, information-dense sentence. It front-loads the core action and resource, then adds rate limit, read-only status, and endpoint in a compact format. No extraneous words.

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 zero-parameter, no-output-schema list tool, the description is sufficiently complete. It specifies what is listed, where (connected account), the HTTP method, read-only behavior, and rate limiting. Nothing essential is missing for an agent to invoke it 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 input schema has no parameters, so schema coverage is trivially 100% and the baseline is 4. The description adds useful context by identifying the target resource ('Stripe products/plans') and scope ('connected account'), which helps the agent understand what the tool operates on even without parameters.

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 ('List') and a clear resource ('Stripe products/plans on the connected account'). It differentiates from sibling tools by naming the exact domain (Stripe products/plans) and the account scope, so an agent can distinguish it from listCoupons, listTransactions, etc.

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 clearly conveys when to use this tool: to retrieve Stripe products/plans for the connected account. It does not explicitly exclude alternatives or name siblings, but its stated resource and scope make the use case unambiguous enough given the sibling set.

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