blender_mesh_fill

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

No annotations exist, so the description carries the full behavioral burden. It states the core behavior and supported fill methods, but does not disclose that the operation mutates the mesh, what conditions cause failure (e.g., invalid or non-boundary edge indices), or whether the result is reversible. For a geometry-modifying 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?

Two short sentences with no filler; the action is front-loaded and the method list is useful. Every word earns its place.

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 input schema is fully self-describing and the purpose is clear, so the tool is minimally callable. However, the description omits side-effect and failure-mode context needed for dependable use, and there is no output schema to clarify return behavior. It is adequate but not complete.

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?

Schema description coverage is 100%, so the schema already documents object_name, edge_indices, fill_type, and use_beauty. The description's mention of n-gon, triangle fan, and grid fill paraphrases the enum without adding new semantic detail, so the baseline 3 applies.

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?

Description opens with a specific verb and resource ('Fill boundary edges with faces') and adds synonyms ('cap holes, close open geometry') that make the intent unmistakable. This clearly differentiates it from sibling operations like bridge, dissolve, or extrude.

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 phrase 'cap holes, close open geometry' establishes clear context for when the tool should be used. It does not explicitly name sibling alternatives or exclusion criteria, so it stops short of a 5.

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