stripe_customers

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention any behavioral traits such as mutation, idempotency, rate limits, authentication requirements (beyond the key), or error scenarios. The description is silent on what happens during creation or listing.

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 short (one sentence), which makes it concise but at the cost of essential details. It is front-loaded with the actions, but lacks structure or elaboration. It is under-specified rather than optimally concise.

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?

Given the tool's complexity (8 parameters, two operations) and lack of output schema, the description is very incomplete. It does not explain return values, pagination, error handling, or provide examples. An agent would struggle to use this tool correctly without additional information.

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 low (38%), and the description adds no additional meaning to the parameters beyond what the schema already states. It does not explain the purpose of undocumented parameters like limit, email, name, phone, or description, nor how they affect list or create actions.

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 specifies the resource (Stripe customers) and the two actions (list or create). It is specific and distinguishes itself from sibling tools that handle other Stripe resources. However, it is minimal and does not elaborate on the scope of listing or the creation process.

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 list vs create, or when to prefer this tool over alternatives. No context about prerequisites, typical use cases, or exclusion criteria. The agent has to infer usage from the parameter schema alone.

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