spine_offset_bone_timeline_values

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

No annotations are provided, so the description carries the full burden. It says 'adjust' but does not disclose whether changes are destructive, requires permissions, or what happens on failure. The dryRun parameter is not mentioned, which is critical for understanding test behavior.

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 short (two sentences) and front-loaded with purpose. However, it could include more context without being verbose, such as mentioning the dryRun parameter or the supported timeline types.

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 10 parameters, nested objects, no output schema, and low schema coverage, the description is severely incomplete. It does not explain the role of each parameter, the meaning of offset/scale for different timeline types, or the effect of dryRun. The tool is complex but the description is minimal.

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 10%. The description only mentions offset and scale, but does not elaborate on filePath, animation, bones, timeline, range, dryRun, or other parameters. The agent receives little extra meaning beyond the schema.

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 batch adjusts bone timeline values with offset or scaling. It uses specific verbs ('批量调整', '增加偏移或按比例缩放') and distinguishes from sibling tools focused on individual keyframe operations or different aspects of animation editing.

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 tool versus alternatives like spine_scale_keyframe_times or spine_shift_keyframes. The description does not mention prerequisites, nor does it indicate cases where this tool is inappropriate.

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