insumer_buy_merchant_credits

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

Discloses non-refundable, owner-only nature, wallet registration behavior, auto-detection of tokens on EVM/Solana, BTC conversion with confirmation, and volume discounts. No annotations, so description fully covers behavioral traits.

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?

Single paragraph packs many details efficiently. Could be restructured for readability (e.g., bullet points for discounts), but it's not overly verbose and all information is relevant.

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?

Covers key aspects: payment methods, wallet registration, volume discounts. However, lacks explanation of return values or post-purchase state (e.g., how credits are reflected) since no output schema.

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 covers 100% of parameters with descriptions. Description adds context like volume discounts and wallet registration but doesn't significantly enhance parameter understanding beyond schema.

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 it buys merchant verification credits with specific tokens (USDC, USDT, BTC) and includes volume discounts. It differentiates from siblings like 'insumer_buy_credits' by specifying 'merchant' and 'verification'.

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?

Provides clear context: owner-only, minimum amount, wallet registration on first purchase, and how to update wallet. However, doesn't explicitly say when not to use or compare to alternatives like 'insumer_buy_key'.

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