spine_delete_animation

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

No annotations are provided, so the description must disclose behavior. It mentions high-risk nature and confirm requirement, but fails to detail side effects, irreversibility, or what happens during deletion. The description partially compensates but is insufficient for a destructive 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 extremely concise with two short sentences. No redundant information is present; every word serves a purpose.

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?

Given the tool has 6 parameters, 3 required, and no output schema, the description is far too minimal. It does not describe return values, effects on the document, prerequisites, or post-conditions. A complete absence of context for a complex destructive operation.

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 only 17% (only filePath described). The description adds no parameter-level details beyond the confirm flag requirement. It does not clarify 'animation', 'dryRun', 'expectedHash', or 'allowUnsupportedVersion', leaving most parameters unexplained.

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 clearly states '删除动画' (Delete animation), which is a specific verb-resource pair. It distinguishes this tool from sibling tools like spine_create_animation or spine_clone_animation by implying destruction.

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 warns that this is a high-risk operation and requires confirm: true, but it does not provide guidance on when to use this tool versus alternatives (e.g., spine_delete_keyframe_range) or when not to use it. No explicit usage context is given.

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