Rotate Fill Light Clockwise

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

No annotations are provided, so the description carries full burden. It discloses the auto-query behavior, which is a useful trait beyond the basic rotation. However, it doesn't mention any other side effects, permissions, or return values. For a simple tool, this is adequate but not overly rich.

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 sentences: the first clearly states the action and effect, the second adds a behavioral nuance. No unnecessary words, information is 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?

For a simple action tool with one optional parameter and no output schema, the description covers the key aspects: what it does, the effect (azimuth decrease), and an important behavioral note (auto-query). It is complete for an agent to use correctly.

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 description adds context that the degrees parameter defaults to 10°, which matches the schema description. It also explains that clockwise rotation decreases azimuth, adding meaning beyond the schema. With 100% schema coverage, baseline is 3, and this extra context justifies a 4.

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 action: rotate the fill light clockwise, and specifies that it decreases azimuth. This uses a specific verb and resource, and the direction distinguishes it from its counterclockwise sibling.

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 mentions that the tool automatically queries fresh state, which guides when to use it (when state freshness matters). However, it does not explicitly state when not to use or provide alternatives, though the name and siblings make the direction clear.

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