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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about side effects, whether the 'burn' is irreversible, how secret_input is handled, or what is returned. 'Run the bound task' implies execution but says nothing about consequence or 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?

A single short sentence, so there is no waste and the key concept is front-loaded. However, the brevity is under-specification rather than efficiency: nothing essential is explained in the space saved.

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 tool with a free-form nested object parameter, an unmentioned secret_input, no output schema, and no annotations, the definition leaves an agent guessing about call shape and outcome. The only real aid is the hint that the credential comes from minting.

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 the nested task_spec object has no defined shape. The description only maps 'credential' to 'minted credential' and leaves task_spec unexplained and secret_input entirely unmentioned, so half the parameters remain opaque.

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?

States a verb (run) and an object (the bound task) and hints at the minting prerequisite via 'minted credential', which loosely separates it from burn_mint. But 'bound task' and 'burn_run' are undefined jargon, so an agent cannot tell precisely what execution means here versus burn_spawn or burn_burn.

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 when-to-use or when-not-to-use guidance, and no mention of the alternatives among burn_mint, burn_verify, burn_gate, or burn_spawn. The only implicit routing is 'minted credential', which an agent must infer implies running burn_mint first.

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