Rotate Model Counterclockwise

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

Discloses that tool auto-queries fresh state before rotating, ensuring accuracy even after manual interaction. No annotations exist, so description adds some behavioral context but lacks details on side effects or return values.

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 efficient sentences; purpose front-loaded, then auto-query detail. No wasted 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?

Tool has one simple parameter, no output schema. Description explains rotation axis, direction, incrementality, and auto-query behavior. Sufficient for a simple manipulation tool.

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 coverage is 100%, baseline 3. Description adds default value (10°) and clarifies that rotation is relative to current rotation, adding meaning beyond schema.

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?

Clearly states verb (rotate), resource (model), axis (Y axis), and direction (counterclockwise). Distinguishes from sibling rotate_model_clockwise by specifying counterclockwise.

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?

Implied usage for yaw rotation counterclockwise; mentions relative to current rotation but does not explicitly state when to use vs rotate_model_clockwise or other rotation tools.

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