firestarter_fund_wallet

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

The description goes well beyond the annotations by explaining the Stripe Checkout flow, the fact that the wallet credits only after payment completes, the $1.00 minimum, and the notable side effect that drops go live immediately once funded. This gives the agent a strong mental model of the tool's behavior.

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 longer than strictly necessary, but every sentence adds value: purpose, mechanism, side effects, return value, and usage trigger. It is front-loaded with the core action and then provides supporting detail.

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 single-parameter tool with no output schema, the description is complete. It explains what the tool returns, what happens after payment, how the wallet relates to drops, and when to invoke it. Nothing essential is missing.

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 coverage is 100% and the schema already describes amount_cents with its minimum. The description repeats the $1.00 minimum but adds no new parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'Deposit money into your drop wallet via Stripe Checkout.' It clearly distinguishes this from related wallet tools like firestarter_wallet_balance and firestarter_withdraw_wallet, and even ties it to firestarter_create_drop.

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 explicitly states when to use it: 'Use when an owner asks to fund/top up/add money to their drop wallet.' It does not explicitly name alternatives or when-not-to-use conditions, but the stated trigger is clear enough for an agent to route correctly.

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