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

With no annotations, the description carries the full behavioral burden. It discloses one conditional outcome ('signed receipt only when every shard is accounted') but omits destructive or irreversible effects, credential/auth requirements, side effects on child receipts, and failure behavior.

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 short and front-loaded, but it is cryptic and under-specified rather than concise. Terms like 'shard' and 'accounted' are unexplained, so brevity costs clarity.

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?

For a likely destructive agent-burning operation with no annotations and no output schema, the description leaves out side effects, auth requirements, return format beyond a conditional receipt, and parameter meanings. It is not complete enough to call safely.

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 0% and neither parameter is described in the schema. The description never mentions 'credential' and does not explicitly map 'child_receipts' to 'every shard accounted,' leaving an agent with no guidance on what values to supply.

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 names an action ('Burn') and an object ('an agent'), so it is not a pure tautology. However, 'burn' is undefined in this context and the description does not distinguish this tool from siblings such as burn_run, burn_verify, or burn_spawn.

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 gives no when-to-use or when-not-to-use guidance and names no alternatives despite six sibling tools. The receipt condition is a behavioral precondition, not routing guidance.

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