stripe_subscriptions

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

The description only indicates a read operation, but fails to disclose required authentication (secret_key), pagination behavior (starting_after parameter), or any potential side effects. With no annotations, the description carries the full burden but provides minimal transparency.

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 sentence, which is concise but lacks any structure or additional details. It is not wasteful, but it could be slightly expanded with front-loaded key information.

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 6 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain pagination, filtering, return format, or authentication requirements, making it difficult for an agent to use 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?

With only 17% schema description coverage (status parameter only), the description adds no additional context for the remaining 5 parameters. It does not explain the purpose of secret_key, limit, starting_after, customer, or price, which is insufficient given the low schema coverage.

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 action (list) and resource (Stripe subscriptions). It is specific enough to identify the tool's purpose, but lacks differentiation from sibling Stripe tools like stripe_invoices or stripe_charges.

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 versus other Stripe tools, such as for filtering by customer or status. No alternatives or exclusions are mentioned.

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