Reduce a model's triangle count

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

With no annotations provided, the description carries full responsibility. It discloses important behaviors: keeps existing texture, works on any completed model, handles detailed/sculpted and other models differently, and selects the right endpoint. It does not mention authentication needs or rate limits, but covers key 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?

The description is concise with three short paragraphs, each serving a distinct purpose: purpose and differentiation, behavior, and example budgets. No unnecessary words or 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?

Given the complexity (6 parameters, no output schema, no annotations), the description covers the essential purpose, usage guidance, and behavioral details. It lacks explanation of return values and some parameters, but provides enough context for typical use.

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%, so the description must compensate. It explains the target triangle parameter by providing typical game budgets, adding context. However, it does not explain the required submission_id or optional parameters like dest, wait, project_id, focus_on_node_names. Partial compensation.

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 tool's purpose: 'Cut a model down to a triangle budget.' It uses specific verbs and resource ('reduce', 'model'), and explicitly distinguishes from a sibling tool (thrixel_detail_model) by explaining why this should be preferred (free, fast, lighter version of the same 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?

The description provides clear guidance on when to use this tool: always use it instead of re-running thrixel_detail_model for lightening. It includes typical triangle budgets for game assets. However, it does not explicitly state when not to use it or mention alternatives beyond the one sibling.

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