burn_erc20_tokens

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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions the two burn mechanisms but does not warn that burning is irreversible, may fail for tokens without a burn function, or may be prohibited for some contracts. Critical safety information is missing for a destructive operation.

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 a single, front-loaded sentence that directly states the action and mechanism. Every word earns its place, and there is no fluff or redundancy, making it an example of effective conciseness.

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?

This is a complex, irreversible transaction tool with no annotations and no output schema. The description explains the mechanism but fails to mention the permanent nature of burning, the need for gas/network fees, potential token-specific failures, or default network behavior. This is insufficient for an agent to fully understand the tool's implications.

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 parameters (amount, network, privateKey, tokenAddress) are fully documented in the schema. The description adds no additional parameter semantics beyond the tool's general purpose, so a 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 clearly states the tool's primary action ('Burn ERC20 tokens') and includes the specific mechanism (send to zero address or call burn function if available). This distinguishes it from sibling tools like transfer_erc20 or approve_token_spending, making the purpose unmistakable.

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?

No guidance is provided on when to use this tool versus alternatives. While the name implies burning, there is no explicit context, exclusions, or references to other token-operations tools, leaving the agent to infer appropriate usage.

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