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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotent, so the agent knows this mutates state. The description adds nothing beyond that — it doesn't say whether the original shapes are consumed or replaced, whether an existing symbol with the same name collides, or how instances are created afterwards.

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 with no padding, but its brevity comes at the cost of under-specification rather than efficiency. The core action is front-loaded, which is the one structural strength.

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?

A destructive, non-idempotent mutation with no output schema and no documented parameters needs more than one sentence. The agent cannot tell what the return value represents, whether shapes are destroyed or converted in place, or what failure modes exist.

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% for two parameters. The description only weakly implies the plural-shape input ('shapes') and never explains shape_ids format/ordering or what omitting the optional name does (auto-naming vs. error). The schema carries no meaning of its own, so the description should compensate and does not.

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 and resource: turns shapes into a symbol, which is distinguishable from group/ungroup and from place_symbol/detach_symbol/list_symbols. It does not explicitly name those siblings, but the operation itself is unambiguous.

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 guidance on when to use this versus grouping shapes or creating a symbol instance, and no prerequisites (selection state, artboard context) are mentioned. The agent must infer that the shapes already exist and are referenced by id.

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