chimerax_turn

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

With no annotations, the description carries the burden. It discloses that frames=1 results in an instant rotation and that frames must be >= 1, which is useful behavioral context. However, it does not mention whether the rotation affects the session state, requires an active session, or has side effects.

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 compact and well-structured with an Args and Returns section. Every sentence adds information, and the format is easy to scan.

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 rotation tool, the description covers purpose, all parameter semantics, and basic return. It is missing some context about prerequisites (e.g., need an open session) but remains sufficient given the low complexity. An output schema exists, so return details are not fully required.

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 0%, but the description fully compensates by explaining each parameter: axis accepts x/y/z, angle is in degrees, frames is an integer >= 1 with default 1. It even explains the meaning of frames=1 (instant), adding clear semantic value beyond the raw 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?

The description clearly states a specific verb and resource: 'Rotate the view around an axis.' This is unambiguous and distinguishes it from sibling tools like chimerax_view or chimerax_reset.

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 rotating the view but does not explicitly state when to use it over alternatives or what other tools might be better for related tasks. No exclusions or alternative references are provided.

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