retopology

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

No annotations provided. Description discloses three methods (quadriflow, voxel, shrinkwrap) with their outputs and use cases, plus target face count and extra params. Does not mention side effects or permissions, but is fairly transparent.

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?

Description is concise with a clear header and structured parameter list. Every sentence adds value, no wasted words.

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?

Output schema exists, so return values documented elsewhere. Description covers purpose, all parameters, and methods. Lacks error conditions or prerequisites, but is sufficient for typical use. Complexity is moderate.

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%, but the description explains all 4 parameters: mesh_name, method (with examples), target_faces (default), and params (with per-method examples). Adds significant value beyond 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 'Retopologize a mesh for clean animation-ready topology' with a specific verb and resource, and parameter details differentiate it from siblings like 'remesh' and 'decimate'.

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 explicit guidance on when to use this tool vs alternatives like 'remesh' or 'decimate'. The purpose is implied but not contrasted with related tools.

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