create_facial_topology

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

No annotations are provided, so the description must carry full burden. It does not disclose whether the tool creates a new object or modifies existing geometry, nor any required modes or selection. The behavioral details are minimal beyond the name.

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 concise with a clear first sentence stating the core purpose, a brief importance note, and a structured parameter breakdown. Every sentence adds value and is well-organized for agent comprehension.

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 description covers purpose, importance, and parameter details well. However, it lacks information about prerequisites (e.g., whether an object must be selected or if edit mode is required) and does not explain what the tool returns (though an output schema exists). For a creation tool, some behavioral context is missing.

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 0% description coverage and all parameters are strings with defaults. The tool description provides detailed meaning for each parameter: 'feature' lists three options with descriptions, 'params' gives explicit JSON structures for eye and mouth, and 'location' indicates it's a JSON center position. This adds essential context missing from 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 clearly states the verb ('create') and resource ('facial topology with concentric edge loops'). It also explains why it's important ('critical for blend shape deformation'), which adds context. This distinguishes it from sibling tools like 'topology_edge_loops' that might create generic edge loops.

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 does not explicitly state when to use this tool versus alternatives. It hints at use for blend shape deformation, but there is no guidance on when not to use it or comparison with other face topology tools like 'ft_setup_face_vertex_groups' or 'topology_edge_loops'.

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