insumer_buy_key

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

No annotations, but description covers all behavioral traits: payment methods, wallet addresses, auto-detection, BTC conversion, one key per wallet, volume discounts, and non-refundable nature.

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?

Compact paragraph with all essential info, though slightly dense. No redundancy, but could be broken into bullets for clarity.

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?

Comprehensive coverage of payment methods, wallets, discounts, and exceptions (non-refundable, one key per wallet). Sufficient 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?

Schema coverage is 100%, and description adds context: txHash as proof, chainId details, amount minimum and BTC exception, appName as key name.

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 verb 'Buy' and resource 'new API key' with specific payment methods, and distinguishes from sibling 'insumer_buy_credits' for topping up.

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?

Explicitly states no auth required and 'Agent-friendly: no email needed.' Also provides alternative: 'One key per wallet — use insumer_buy_credits to top up.'

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