spine_delete_keyframe_range

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

No annotations provided; description only mentions deletion and filtering but fails to disclose destructive nature, irreversibility, or behavior after deletion. DryRun parameter is not explained in the description.

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?

Single concise sentence that front-loads the purpose. No unnecessary words, though it is in Chinese and may benefit from slight expansion for English clarity.

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?

With 7 parameters, nested objects, and no output schema, the description omits crucial details like return values, side effects, and how dryRun works. Incomplete for safe invocation.

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 low (14%); description adds meaning for the time range and filtering concepts, but does not elaborate on the structure of targets (e.g., targetType enums, names, timelines). Partially compensates.

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 it deletes keyframes in a time range with optional filtering by bone, slot, or draw order, distinguishing it from siblings like spine_remove_keyframe (single) and spine_copy_keyframe_range (copy).

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 explicit guidance on when to use this tool versus alternatives like spine_remove_keyframe. The description implies its use for range deletion but lacks context for prioritization.

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