Explode Block

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds meaningful behavioral context beyond that: the operation transforms a block reference into its individual component entities, clarifying the expected outcome of the destructive action. It does not detail edge cases such as nested blocks or attributes, but for a one-step explode operation this is reasonably transparent.

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 concise sentence that front-loads the action and the target resource. Every word contributes meaning; there is no filler, repetition, or unnecessary background.

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 one required parameter, an output schema, and annotations that already declare destructive behavior, the description is complete enough for an agent to understand what the tool does and invoke it correctly. The schema covers the parameter, and the description covers the operation's essence.

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 100%, and the schema already documents the handle parameter as a block reference (INSERT) entity handle. The tool description itself does not add parameter-specific detail, but because the schema fully covers the parameter, the baseline of 3 is appropriate.

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 specific verb ('Explode'), a precise resource ('block reference'), and a clear outcome ('into its individual component entities'). The description clearly distinguishes this from the many block_* sibling tools such as block_list, block_insert, and block_find_references, which perform different operations.

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 explicit when-to-use or when-not-to-use guidance is provided, and no alternative tool is named. However, the tool's unique purpose among siblings implies usage when a block reference must be decomposed into editable component entities, so the guidance is somewhat implied rather than missing entirely.

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