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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation. Beyond that, the description discloses the actual money flows (Card/USD -> custodial USDC on onramp, USD payout via Stripe Connect on withdraw), which is meaningful context the annotations can't convey. It still omits auth/permission requirements and reversibility, keeping it below a 5.

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?

Front-loads the purpose and flows in a single dense sentence, then lists the action enum. The action list duplicates the schema enum, which is mildly redundant, but overall there is little waste.

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 multi-action financial tool with five params and no output schema, the description covers the onramp and withdraw paths but never explains the 'receipt' action (only listed in the enum) or what status returns. It is adequate but leaves clear gaps an agent would have to probe at runtime.

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 the parameter meanings (amount currency meaning, network default, agent_id, receipt_id) are already documented in the schema. The description's restatement of the action enum adds nothing beyond the structured field, so the 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 resource (Stripe Fiat-to-Crypto onramp, Stripe Connect Transfers) and the three core verbs (check status, onramp deposit, withdraw). It clearly distinguishes this as the money-movement tool. Sibling differentiation is weak only because there is no close payment-themed sibling to contrast against, so the description doesn't need to route elsewhere.

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 enumerates the four actions and their intents, which implies when each is used (status to check, onramp to deposit, withdraw to cash out). However it gives no explicit when-not guidance, prerequisites, or conditions selecting between them, leaving the agent to infer the triggers from the action names.

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