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

The description adds useful behavioral context beyond annotations: the result is a hosted, free download URL; format depends on target; .glb and .bbmodel include all animations; GIF/sheet/MP4 exports require an animation name. This is meaningful context that helps the agent predict behavior. No contradiction with the idempotent or non-destructive annotations.

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 compact, front-loaded with the primary action and output, and every sentence carries useful information. The target format rules and animation caveat are stated efficiently without unnecessary prose.

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 rich input schema, output schema, and annotations, the description is complete enough for correct invocation. It covers the core export purpose, target-specific formats, animation behavior, and the free hosted URL, leaving no critical ambiguity for an agent to call this tool correctly.

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 100%, so the schema already documents all parameters well. The description adds a bit of semantic value by clarifying target-to-format mapping and animation inclusion, but most parameter meaning is already present in the schema, so the additional contribution is limited.

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 a specific action and resource: exporting a Low-Poly model and returning a hosted download URL. It also distinguishes by output format (e.g., .glb, .bbmodel, resource pack), though it does not explicitly name an alternative sibling like get_lowpoly_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 implies when to use the tool: when you need an exported Low-Poly model for a specific engine or tool. It also gives practical targeting guidance (e.g., Blender gets .glb, Blockbench gets .bbmodel) and notes animation requirements, but it does not explicitly explain when to choose this over sibling tools or 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.