flip_normals

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

The description explains the core behavior: it flips normals and the optional parameter defaults to flipping all faces. However, it does not state that the mesh is modified in-place, whether the operation is undoable, or any potential side effects. With no annotations, the description carries full burden and partially meets it.

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 extremely concise with two sentences plus a parameter list. Every sentence adds value, and there is no redundant information. It is well-structured and easy to parse.

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 description is adequate for a simple operation but lacks important details: no mention of return values (success/failure), error conditions (invalid name, indices out of range), or feedback. In the context of a 2-parameter tool with no output schema, more completeness would be helpful.

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 schema: 'name' is clarified as 'Mesh object name', and 'face_indices' is explained as 'Comma-separated face indices (flips ALL faces if omitted)'. Given 0% schema coverage, the description fully compensates.

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 it flips face normals on a mesh and explains the effect: 'reverses which side is the outside'. This is a specific verb+resource, and it distinguishes this tool from sibling mesh operations like extrude, inset, or triangulate.

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 guidance is given on when to use this tool versus alternatives, such as recomputing normals or using other mesh editing tools. It does not mention prerequisites (e.g., the mesh must have faces), nor does it provide examples of typical use cases.

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