blender_ai_fix_mesh_issues

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

With no annotations provided, the description carries the full burden of explaining behavior. It does enumerate the repair operations and the pre-export context, which is useful. However, it does not disclose that the tool modifies the mesh in place, whether operations like interior-face removal are destructive, or what kind of result or confirmation the agent can expect.

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 two concise sentences with no filler. The first sentence front-loads the action and scope, and the second adds a clear use case, so every word contributes meaningful information.

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 mesh-repair tool with six fully documented parameters and one required object name, the description provides enough context to select and invoke it correctly. It covers what the tool does and when it is intended to be used. It does not mention in-place mutation or return behavior, but those gaps are relatively minor given the rich schema.

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 100% description coverage and each parameter already includes a clear description and default value. The tool description adds no new parameter-level information, though its listed issues ('holes', 'inverted normals') do loosely map to the boolean parameters. This matches the baseline for high schema coverage.

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 verb and resource: fixing common mesh problems, and it enumerates specific issue types (non-manifold edges, holes, inverted normals, interior faces). It also adds the intended context of repairing AI-generated meshes before export. It does not explicitly differentiate itself from similar siblings like blender_ai_mesh_cleanup, so it stops short of a 5.

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?

It explicitly gives a use case: 'Useful for repairing AI-generated meshes before export.' This gives clear context for when the tool is appropriate. However, it does not mention when not to use it or name any alternatives, so it lacks the explicit exclusions needed for a 5.

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