hedera_burn_token

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

No annotations provided. Description omits behavioral details: requires burn key, destroys tokens, creates an unsigned transaction needing signing/submission. Fails to disclose mutation and permissions.

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 sentence, concise but lacks structure. No bullet points or additional details. Could be improved with clear sections but not overly verbose.

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?

Given 4 parameters, no output schema, no annotations, and the tool is a mutation, the description is incomplete. Missing workflow (unsigned transaction), permissions, effect on supply, and parameter constraints.

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 50% (amount, serials described). Description adds no extra meaning; doesn't clarify that tokenId is the token to burn or that at least one of amount/serials is logically required. No explanation of exclusivity.

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?

Description clearly states it builds a burn of fungible amount or NFT serials. Verb 'Build (unsigned)' indicates transaction creation. Distinguishes from minting or transfer siblings, but could be more explicit about the transaction-building nature.

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 on when to use this tool vs alternatives like hedera_wipe_token. No mention of prerequisites (e.g., token association, treasury role) or that burning reduces supply permanently.

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