stripe_products

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

With no annotations provided, the description must fully disclose behavioral traits. However, it only states the tool lists products, omitting critical details such as whether it is read-only, rate limits, pagination, or authentication requirements. The agent cannot assess safety or side effects.

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 extremely concise at three words, which achieves brevity but lacks necessary detail. It front-loads the core action but is too minimal to be considered well-structured for effective agent use.

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 tool with four parameters, including required authentication and pagination options, the description is incomplete. It does not explain return format (no output schema), filtering, or pagination behavior, leaving the agent with insufficient context to use the tool 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 description adds no meaning beyond the parameter names from the schema (e.g., 'limit' is not explained as a pagination limit, 'active' is not clarified as a filter). Given 0% schema description coverage, the description fails to compensate by defining parameter roles or valid values.

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 'List Stripe products.' uses a specific verb ('List') and clearly identifies the resource ('Stripe products'). It effectively distinguishes this tool from siblings like 'stripe_charges', 'stripe_customers', etc., which target different resources.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., secret_key required), pagination behavior (limit, starting_after), or filtering options (active). The agent is left to infer usage from the schema alone, which lacks explanations.

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