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

With no annotations, the description carries the full behavioral burden. It usefully discloses that this returns an unsigned transaction and is permissionless, and it defines the triggering failure conditions. However, for a burn operation it does not explain what is actually destroyed, whether the action is irreversible, or what the transaction changes.

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 with no wasted words. The key qualifier (unsigned tx, anyone) and the eligibility condition are stated immediately.

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?

The tool has no annotations, no output schema, and 0% schema description coverage. The description covers the purpose and trigger conditions, but it leaves out parameter meaning and the actual effects of burning a failed tranche, so an agent lacks enough context to call it confidently.

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 0%, so the description must define the two required parameters. It references a token and a failed tranche, but it does not explicitly explain what token should contain or what milestone means, nor does it document format or constraints.

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 states a specific verb and resource: it builds an unsigned transaction to burn a failed tranche. It also gives the defining conditions (deadline passed or token did not graduate within 60 days), which lets an agent distinguish this burn operation from the other build_*_tx siblings.

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?

It clearly states when the tool applies: the tranche is failed because its deadline passed or the token did not graduate within 60 days. It also notes that anyone can invoke it. It does not mention alternatives or exclusions, but the usage context is explicit enough.

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