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

The description goes well beyond the destructiveHint and readOnlyHint annotations. It discloses the critical side effects: the group's animation tracks are discarded, children survive at their last positions, and children inherit none of the group's keyframes. This gives an agent an accurate mental model of what is destroyed and what survives.

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 two sentences with zero filler. The first sentence states the core behavior, and the second adds the critical caveat about discarded animation tracks and non-inheritance of keyframes, separated by an em dash for clarity. Every clause earns its place.

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 hierarchy mutation with a full input schema and an output schema, the description covers everything an agent needs to decide and invoke correctly: the resulting structure, what is destroyed, what survives, and the positional inheritance behavior. No essential behavioral detail is missing.

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 coverage is 100%, and the schema already gives strong semantics for both parameters: groupId is described as a bare id without the 'group.' prefix, and projectId as an opaque v4 UUID from list_projects/create_project. The description adds no parameter-specific meaning beyond what the schema provides, so 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?

The description opens with a specific verb and resource — 'Dissolve a group' — and explains the exact structural effect: children are spliced into the group's parent at the group's old position. This clearly distinguishes it from sibling tools like group_layers, set_group_parent, or rename_group by describing the destructive, hierarchy-changing outcome.

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 when to use the tool — when you want to remove a group while keeping its children in the hierarchy — but it never explicitly names alternatives or states when not to use it. For example, set_group_parent is an alternative that preserves the group, but it isn't mentioned. The usage context is clear but left to inference rather than explicit guidance.

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