rhino_flip_mesh_normals

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

No annotations are provided, so the description carries the full burden of disclosing side effects. It only restates the operation without explaining that it mutates the mesh, what happens if no faces are selected, or whether changes are reversible. For a mutating tool, this is a significant transparency gap.

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 short and the primary behavior is front-loaded in the first sentence. The 'Args' block is mostly redundant with the schema and introduces an undocumented controller parameter, preventing a higher score, but the overall structure is still efficient.

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?

The tool is simple and has no required parameters, and an output schema exists, so the return-value burden is lower. However, the description does not explain how 'selected mesh faces' are determined, what state is required in Rhino, or how this differs from related normal-related tools. It is adequate but has clear gaps.

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 input schema has zero properties, so the description does not need to document user parameters. It does mention a 'controller: RhinoController instance' argument that is not present in the schema, which is slightly confusing, but this does not block invocation since no schema parameters are required.

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 action ('Flip') and the target resource ('normals of selected mesh faces'), so an agent can tell what the tool does. It does not explicitly contrast with closely related tools like rhino_unify_mesh_normals or rhino_flip, but the phrase 'selected mesh faces' adds useful specificity.

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?

There is no guidance about when to use this tool instead of related mesh-normal tools, nor any mention of prerequisites such as having mesh faces selected or needing an active Rhino document. The description relies entirely on inference.

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