spine_shift_keyframes

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

No annotations are provided, and the description does not disclose behavioral traits such as whether shifting is destructive, how out-of-range keyframes are handled, or the role of dryRun and expectedHash. Only the basic operation is stated.

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 concise sentence in Chinese, front-loading the core action. It is efficient but could be slightly expanded for clarity without harming conciseness.

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 8 parameters with nested objects, no output schema, and low schema coverage, the description is incomplete. It lacks details on return values, error conditions, or how the shift operation precisely works.

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 13% (only filePath has a description). The tool description does not add meaning to parameters like deltaTime, targets, or dryRun, leaving their semantics unclear.

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 moves keyframes overall forward/backward within specified animation, time range, and target filter. It is a specific verb+resource but does not differentiate from sibling keyframe tools like spine_copy_keyframe_range or spine_scale_keyframe_times.

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 usage for shifting keyframes in time but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or when-not contexts.

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