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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds the concrete outcome—conversion into editable shapes—but does not explain what happens to symbol overrides, nested symbols, the symbol link, or undo 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 a single front-loaded sentence with no filler. It communicates the core outcome efficiently, even though other dimensions lack detail.

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 destructive, non-idempotent one-parameter mutation, the description gives the essential transformation and annotations carry the danger warning. However, it omits important behavioral details such as the effect on symbol overrides and whether the original instance or symbol link is lost.

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 only parameter, shape_id, has no schema description at all. The phrase 'one symbol instance' hints that the ID must identify a symbol instance, but the description never names shape_id, its expected format, or how to obtain it, so it only partially compensates for the 0% schema coverage.

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 gives a specific verb and resource: turning one symbol instance into editable shapes. It distinguishes the operation from siblings like make_symbol or place_symbol by focusing on converting an existing instance, though it does not explicitly contrast with ungroup.

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 implied use is reasonably clear: call this when a symbol instance should become editable shapes. However, there is no explicit when-not guidance, prerequisite that the shape must be a symbol instance, or named alternative such as ungroup or make_symbol.

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