stripe_customers

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

With no annotations, the description must carry full behavioral disclosure. It only states 'list or create' without explaining side effects (creating a customer modifies Stripe data), authentication requirements, pagination behavior for list, or error conditions. This lack of disclosure could lead to misuse.

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 very short, which is concise but lacks detail. It is front-loaded with the essential purpose, but could benefit from a brief structure separating list and create contexts without harming conciseness.

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 8 parameters and two distinct actions, the description is too minimal. It omits crucial context: which parameters are for list vs create, pagination behavior, and expected response format (no output schema). The agent may struggle to correctly invoke the tool.

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 low (38%), and the description adds no additional meaning to parameters. It does not clarify that email, name, etc., are for creation, or that limit and starting_after are for pagination. The action enum is clear from schema, but the description does not leverage it to explain parameter groupings.

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 clearly states the tool manages Stripe customers with two actions: list and create. It distinguishes from sibling tools that focus on other resources (charges, invoices, etc.). However, it does not specify which parameters correspond to which action, and the title is null.

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?

No guidance is provided on when to use this tool vs alternatives (e.g., other Stripe tools) or when to choose list vs create. Prerequisites such as requiring a secret_key are not mentioned. The agent must infer from parameter names and enum.

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