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

With no annotations, the description must carry the full behavioral burden. It discloses only that a shard custody transfer occurs, but says nothing about permissions implied by the credential parameter, what happens to the child or shard afterward, whether the operation is reversible, or what is returned.

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 single sentence is front-loaded and wastes no words, but its brevity comes at the cost of under-specification rather than efficient communication.

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 credential parameter, a nested required object, no annotations, and no output schema, the description is far too thin. An agent lacks the information needed to invoke it correctly or predict its effects.

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%, and the description does not explain either required parameter. It never clarifies what the credential represents or what fields child_task_spec must contain, despite the nested object structure.

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 a specific verb ("spawn") and resource ("child"), and hints at a side effect ("custody of one spawn-grant shard transfers"). However, "child" and "spawn-grant shard" are undefined jargon, so an agent cannot tell what is actually being created or how this differs meaningfully from siblings like burn_run or burn_mint.

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?

There is no guidance on when to use this tool versus burn_run, burn_mint, or burn_gate, nor any stated preconditions or exclusions. The implied usage is "when you want to spawn a child," which is circular given the undefined term.

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