explode_entity

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It fails to state that exploding is likely destructive (replaces the original with components) or mention any side effects, limitations, or prerequisites for the input entity. This is a significant gap for a mutation tool.

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, well-structured sentence that immediately states the action and target. It is concise, front-loaded, and contains no filler words.

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?

Despite the presence of an output schema, the description omits crucial information about the operation's effect on the original entity, error conditions, or compatibility with nested objects. For a destructive command, the missing contextual details make the description incomplete for an agent to invoke 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?

The input schema only defines 'handle' as a string with no additional description, and the tool description does not mention the parameter at all. With 0% schema description coverage, the description must compensate, but it provides zero semantic information about what 'handle' is or where to get it.

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 uses a specific verb 'Explode' and clearly identifies the resource types (block/polyline/dimension) plus the outcome ('into its components'). This distinguishes it from sibling tools like break_entity or trim_entity, making the tool's purpose very clear.

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?

The description implies the tool is used for the listed entity types, but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare against alternative decomposition methods. The context is somewhat clear but lacks exclusions or alternatives.

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