set_clip_rotation

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

The description only states it 'sets' a property, aligning with the readOnlyHint=false annotation. It does not disclose behavioral traits like whether it overwrites existing rotation, what happens if the clip has no motion effect, or any side effects. With minimal annotations, the description carries the burden and falls short.

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, clear sentence with no wasted words. It is appropriately front-loaded and efficient.

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?

For a simple setter tool with two fully documented parameters and no output schema, the description is mostly adequate. However, it lacks any mention of return values or side effects, which would be helpful for complete context.

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 input schema already provides descriptions for both parameters (degrees and node_id) with 100% coverage. The description adds no additional meaning or context beyond what the schema provides, resulting in a baseline score of 3.

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 sets the Rotation property on a video clip's Motion effect, using a specific verb and resource. It distinguishes itself from sibling tools like set_clip_position or set_clip_scale.

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 setting rotation but provides no explicit guidance on when to use this tool over alternatives such as set_clip_properties or when the clip lacks a motion effect. No when-not-to-use or prerequisites are mentioned.

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