Retrieve and filter Stripe prices by active status, product, type, and pagination to support billing and subscription workflows.
List Stripe prices.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | one_time or recurring | |
| limit | No | ||
| active | No | ||
| product | No | ||
| secret_key | Yes | ||
| starting_after | No |
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds nothing beyond that: no mention of pagination behavior, despite limit/starting_after parameters, and no note that a Stripe secret key is needed. It neither contradicts nor enriches the annotations.
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?
A single short sentence, front-loaded with verb and resource, so nothing is wasted. However, its brevity reflects under-specification rather than disciplined 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 6-parameter tool with a required secret_key, no output schema, and no explanation of pagination or filtering, one sentence is not enough. The annotations cover safety, but an agent still lacks the information needed to invoke it well.
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 only 17% — just the 'type' enum is documented — leaving limit, active, product, secret_key, and starting_after unexplained. With low coverage the description is expected to compensate, but it mentions no parameters at all, so an agent gets no help on filtering or pagination semantics.
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?
'List Stripe prices' states a specific verb (List) and resource (Stripe prices), which cleanly separates it from siblings such as stripe_products, stripe_customers, and stripe_subscriptions. It lacks any scope detail (all prices? active only?), but the core purpose is unambiguous.
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 gives no guidance on when to use this versus alternatives like stripe_products, nor when the type/active/product filters matter. An agent must infer usage entirely from the tool name and schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.