mesh.edge_face_add

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

No annotations exist, so the description must disclose behavior. It only states the basic action, omitting details like whether it modifies existing geometry, requires specific selection types, or has destructive effects. The agent has no insight into side effects or constraints.

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, which is front-loaded and efficient. However, it is too vague to be fully useful; it could be more informative without losing conciseness.

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 tool's complexity (mesh editing with one parameter and no output schema), the description is insufficient. It does not explain prerequisites (e.g., edit mode, selection) or what exactly constitutes an edge or face addition, leaving critical gaps for an AI agent.

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 one optional parameter 'object', and the description does not mention it at all. With 0% schema description coverage, the description should clarify the parameter's role, but it adds no value 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 states the tool creates an edge or face from selected elements, which clearly identifies the action and resource. It distinguishes from siblings like mesh.fill and mesh.extrude, but lacks specificity on what 'selected elements' refers to (vertices, edges, faces).

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 provided on when to use this tool versus alternatives like mesh.fill or mesh.extrude. There is no mention of prerequisites, such as being in edit mode or having a specific selection.

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