remesh

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

The description lacks details on whether the operation is destructive, how it affects UVs or vertex colors, and any prerequisites. With no annotations, the description should disclose these behavioral traits.

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 efficient sentences, front-loaded with purpose, no redundancy.

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?

Covers modes and voxel_size impact but omits output details, object constraints, and any behavioral context. Adequate but not comprehensive for a tool without output schema.

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?

Description adds meaning for 'mode' (lists values) and 'voxel_size' (explains trade-off), compensating for 0% schema coverage. However, 'name' parameter is left unexplained.

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 clearly states 'Remesh an object to create clean, uniform topology,' which is specific and includes modes. However, it doesn't differentiate from the sibling tool 'sculpt_remesh,' which likely performs a similar operation in a different context.

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 versus alternatives like decimate, retopology, or sculpt_remesh. The description lists modes but doesn't specify use cases or prerequisites.

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