flip_normals

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

No annotations are provided, so the description must carry the burden. It states the core behavior (flip all face normals) but omits details such as whether it is destructive, requires a specific mode, or works on multiple objects. The description is minimally adequate.

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 sentence, very concise and to the point. While it could be improved by including parameter details, it efficiently conveys the core purpose and use case without extraneous text.

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 the single required parameter and no output schema, the description lacks completeness. It does not specify what the 'name' parameter expects, nor does it cover error conditions, applicability to selections, or other behavioral nuances needed for a fully self-contained description.

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 only one parameter ('name') and 0% schema description coverage, the description does not explain what 'name' refers to. It says 'Flip all face normals of a mesh,' but does not clarify if 'name' is the object name, mesh name, or something else. This omission hinders proper parameter usage.

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 all face normals') and the resource ('a mesh'), along with a specific use case ('when faces appear inside-out'). It distinguishes itself from other mesh-related siblings by its unique operation.

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 gives a clear usage context ('useful when faces appear inside-out'), implying when to use it. However, it does not explicitly mention when not to use or provide alternatives, which would be beneficial.

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