set_rotation

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

With no annotations, the description bears full responsibility. It discloses the two rotation modes, value formats, and return type, but does not mention side effects, error handling, or whether rotation is absolute.

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 a concise docstring with clear sections for args and returns, no fluff, and front-loaded purpose. Every sentence serves a purpose.

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 no annotations and no visible output schema (though one exists), the description covers the operation well but omits details like error handling, whether rotation is relative, and potential side effects. Still, it is adequate for a simple setter 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?

The description adds significant meaning beyond the input schema, which has 0% coverage. It explains the name, rotation format for each mode (EULER with 3 radians, QUATERNION with 4 values), and mode parameter with default, fully compensating for the schema's lack of descriptions.

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 'Set the rotation of an object', specifying the verb and resource, and distinguishes from sibling tools like set_location and set_scale. It also explains the two rotation modes (EULER, QUATERNION) and value formats.

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 when an object's rotation needs to be set, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives. No prerequisites or context for choosing between EULER and QUATERNION are provided.

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