Rotate Key Light Clockwise

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

The description discloses a key behavioral trait: it automatically queries fresh state before performing the rotation. Since no annotations are provided, this adds valuable context about ensuring accuracy. It does not cover potential side effects or error conditions, but it is sufficient for a simple operation.

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?

Two concise sentences: first states purpose, second adds behavioral detail. No redundant or unnecessary words. Efficiently front-loads the essential information.

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 the simple tool (one optional parameter, no output schema), the description is largely complete. It covers the action and an important behavioral note. Lacks information about error handling or limits, but these are not critical for a straightforward rotation.

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 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it only mentions the default value which is already in the schema. The description's mention of 'current position' indirectly relates to the parameter, but does not enhance understanding.

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 verb 'rotate', the resource 'key light', and the direction 'clockwise' with the effect 'decreases azimuth'. It distinguishes from the sibling tool 'rotate_key_light_counterclockwise' by specifying the exact direction.

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 when to use this tool (to rotate key light clockwise) and contrasts with the counterclockwise sibling. However, it does not explicitly state when not to use it or mention alternative tools for similar effects.

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