rhino_rotate

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

The description only states the basic action and does not disclose any behavioral traits such as whether objects are modified in place, whether prerequisites like object existence are needed, or what the tool returns. Annotations only provide readOnlyHint=false, which is minimal, and the description adds no further context about side effects or operational details.

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 single, concise sentence that immediately conveys the core operation. It is appropriately structured, front-loading the action and key spatial concepts, with no extraneous words. This is exemplary conciseness.

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 mutation tool with no readOnlyHint, the description is inadequate. It lacks essential context such as prerequisites (e.g., whether objects must be selected), potential side effects on the scene, and expected output format. Given the presence of an output schema and the complexity of a 3D rotation, a more detailed description is necessary for correct invocation.

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?

With schema description coverage reported as 0%, the description must compensate for parameter understanding, but it only mentions 'axis' and 'center point' without explaining the meaning of guids, angle_degrees, or the relationship between parameters. It fails to clarify required fields, units, or default behavior, leaving agents to guess critical input semantics.

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 specific action ('Rotate objects') and the mechanism ('around an axis through a center point'), which unambiguously distinguishes it from sibling transformation tools like move, scale, or mirror. It is direct and leaves no doubt about the tool's purpose.

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 provides no guidance on when to use this tool versus alternatives. It does not mention rotation-specific scenarios or exclude cases where other transformations would be more appropriate. An agent must infer usage solely from the tool name, which is insufficient for effective selection.

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