puppet_preset_motion

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

With no annotations, the description must disclose all behavioral traits. It explains the effects of cycles and intensity parameters and lists presets, but does not cover side effects (e.g., file overwriting), error handling, permission requirements, or the meaning of the cryptic default duration format ('300300/30000s').

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 concise: one purpose sentence, a bullet list of presets with explanations, and a clean Args list. Every element adds value with no unnecessary words.

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?

The description covers all parameters and preset semantics, but lacks details on return values (though an output schema exists), error conditions, prerequisuites (e.g., rig format), and the unusual duration default. It is adequate but not comprehensive for a tool with 7 parameters.

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?

The Args section adds meaningful descriptions for 7 parameters beyond the schema (which has 0% coverage). It explains cycles ('more = faster movement') and intensity with examples (0.5 subtle, 2.0 exaggerated), but does not clarify the duration format or rig_json structure.

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 'Build a puppet scene with a preset motion applied' and lists available presets with descriptions. This distinguishes it from sibling tools like puppet_animate or puppet_build_scene by specifying that a preset motion is applied to a rig.

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 provides presets and their behaviors, implying when to use each, but lacks explicit guidance on when to use this tool versus alternatives or when not to use it. No exclusions or sibling comparisons are given.

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