mesh.fill

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

With no annotations, the description carries full burden but fails to disclose whether the operation is destructive, what happens to the selected edges, or any prerequisites (e.g., edges must form a closed loop). The description is nearly empty.

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 short at 3 words, which is under-specification rather than conciseness. It sacrifices informativeness for brevity.

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 complexity of mesh editing (a mutation tool), the lack of output schema, and no annotations, the description fails to provide essential context about behavior, return values, or side effects. It is completely inadequate.

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 0%, and the description adds no parameter information. The 'beauty' boolean is unexplained (what is 'beauty fill'?), and the 'object' parameter is not clarified. The description adds no meaning beyond the schema.

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 'Fill selected edges' provides a verb and resource, but 'fill' is ambiguous—it could mean creating faces from a closed loop of edges or filling holes. It does not distinguish from related tools like mesh.edge_face_add or mesh.subdivide.

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 mesh.edge_face_add or mesh.subdivide. No prerequisites or context are provided.

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