retexture_model

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

No annotations are provided, so the description carries the full burden. It does disclose that a new variant is produced and the .glb path is returned, but it omits important behavior like whether the task is asynchronous, whether the original model is modified, or whether any polling is required. Some useful context, but not complete.

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 with no filler. The core action is front-loaded, and the output path is stated at the end, making it easy to parse.

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 annotations or output schema exist, so the description is the only guide. It covers the primary workflow and output, but misses two parameters, fails to state whether exactly one source is required, and says nothing about asynchronous execution or status checking. This is a significant gap for a 6-parameter tool.

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?

With 0% schema coverage, the description compensates for four of six parameters by explaining their roles and 'or' relationships. It ignores timeout and enable_pbr, leaving their purpose unclear, so compensation is only partial.

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?

States a specific verb 'Re-texture' and resource 'existing model', clearly distinguishing it from generation, rigging, and animation siblings. It also names the input modes and output path, so an agent understands exactly what the tool does.

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 gives clear context: use this when you want a new variant of an existing model. It also explains the either/or relationships for source and style parameters, which is useful guidance. However, it does not explicitly mention alternatives or conditions when not to use it.

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