spine_apply_pose_keyframes

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

No annotations are present, so the description must fully disclose behavior. It mentions setting keyframes at the same time point but doesn't specify if existing keyframes are overwritten, what the curve parameter does, if the operation is reversible, or if it modifies the file immediately. The dryRun parameter hints at safety but is not explained.

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 short sentence, which is concise but too brief for a tool with 9 parameters. It lacks structure or elaboration, making it insufficient despite being front-loaded.

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 no output schema, no annotations, and 9 parameters with many nested objects, the description is incomplete. It doesn't explain the return value, preconditions (e.g., file must be valid Spine JSON), or postconditions. The tool's complexity demands a more comprehensive description.

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 11% (only filePath has a description). The description adds little parameter context: it implies bones and slots are the targets, but doesn't explain their object structure, the meaning of curve, or the purpose of dryRun and expectedHash. The description fails to compensate for the low schema coverage.

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 the tool batch-sets pose keyframes for multiple bones and slots at the same time point. It uses specific verbs and resources, distinguishing it from sibling tools like spine_set_bone_keyframe which set individual keyframes.

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 does not provide guidance on when to use this tool versus alternatives. For example, it doesn't mention that this tool is for batch operations at a single time point, while spine_apply_pose_sequence might be for sequences over time. No when-not-to-use or prerequisite information is given.

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