stripe_prices_create

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a write to an external system. Beyond that the description discloses nothing behavioral: no note that price objects are immutable, no idempotency or retry guidance, no indication of what side effects or errors to expect. For a financial mutation tool this is a significant gap.

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?

Two short sentences, zero padding, and the core action is front-loaded before the conditional parameter advice. Every clause earns its place.

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?

The 9-parameter schema is fully documented and the description covers the key create-vs-subscription distinction, but there is no output schema and the description says nothing about the returned price object or the immutability of amounts after creation. Adequate for the mechanics, thin on consequences.

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 100%, so every parameter including unitAmount, unitAmountDecimal, taxBehavior and the nested recurring object is already documented in detail. The description's recurring/one-off clarification is essentially a restatement of the schema's own 'Absent, this is a one-off price' note, so baseline 3 applies.

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?

States a specific verb and resource ('Create a price for a product'), which is enough to distinguish it from unrelated siblings like stripe_invoices_create. It does not explicitly distinguish itself from stripe_products_create, which an agent could plausibly confuse it with when setting up a new product.

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 second sentence gives actionable conditional logic for the recurring parameter (include for subscription, omit for one-off), which is real usage guidance. However it says nothing about prerequisites (the product must already exist) or when to reach for stripe_products_create first, so guidance is implied rather than complete.

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