Rotate Model Clockwise

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

Description reveals that the tool queries fresh state before rotation, ensuring accuracy even after manual interaction. This is useful behavioral context beyond the action. No annotations exist, so description carries full burden; it does not contradict any.

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, no redundant information. The first sentence defines the action, the second adds behavioral detail. Every word is meaningful.

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?

No output schema exists, and the description does not explain what the tool returns (e.g., success status or updated rotation). For a mutation tool, this leaves the agent without information on expected results.

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%, so the parameter is already documented. The description adds 'relative to current rotation', which provides additional context but no change to semantics. Baseline 3 is appropriate.

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?

Description clearly states the action: rotate the model clockwise around Y axis (yaw) relative to current rotation. This distinguishes it from the sibling rotate_model_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?

No explicit when-to-use or when-not-to-use is provided. The description implies usage for clockwise yaw rotation, but does not mention alternatives like rotate_model_counterclockwise or nudge_model_roll. Sibling names offer differentiation, but description lacks direct guidance.

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