Edit a 3D model

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

Discloses that it preserves unmentioned parts and works with natural language. No annotations exist, so description carries full burden. Missing details on side effects or costs, but adequate.

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?

Well-structured with three clear paragraphs, front-loaded with purpose. Could be slightly more concise but no unnecessary repetition.

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?

No output schema, so return values are unexplained. Does not clarify async behavior (wait parameter implies but not explicit). Comprehensive for a mid-complexity tool, but some gaps remain.

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 has 0% description coverage. Description only explains 'change' (natural language) and 'focus_on_node_names' (get from inspect_model). Other 4 parameters (dest, wait, project_id, submission_id) are not elaborated.

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?

Clearly states the tool edits existing 3D models via natural-language instructions, emphasizing iteration and preservation. Distinguishes from siblings like thrixel_create_model.

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?

Provides explicit when-to-use (iterate vs. regenerate), applicable inputs (Architect, Auto-fix, Edit results), instruction phrasing tips, and guidance for partial edits via focus_on_node_names.

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