insumer_verify

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

With no annotations, the description carries full burden. It discloses the side effects (consumes 1 merchant credit, auto-creates coupon if Stripe Connect), the return values (tier and discount percentage, never raw balances), and that it is a write operation ('Create'). However, it does not mention authorization requirements or rate limits.

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 three concise sentences that front-load the core action (create code with format and expiry), then return values, then side effects. No redundant or unnecessary information.

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?

While the description covers the code format, expiry, return values, and side effects, it lacks explanation of why three wallet address options exist, and does not mention what happens if no wallet is provided. With no output schema, the description partially compensates by stating return values, but incomplete on parameter details.

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%, so baseline is 3. The description does not add significant meaning beyond the schema's parameter descriptions; it only emphasizes that the code is for a wallet at a merchant, but does not clarify the relationship between the three wallet address fields (wallet, solanaWallet, xrplWallet) or their optionality.

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 'Create signed discount code' with format 'INSR-XXXXX' and 30-min expiry, and distinguishes from sibling tools like insumer_check_discount and insumer_validate_code which are for checking or validating codes.

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 mentions that it consumes 1 merchant credit and auto-creates coupons for Stripe Connect merchants, but does not provide explicit when-to-use or when-not-to-use guidance relative to siblings like insumer_check_discount or insumer_validate_code.

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