preset_download_ambientcg

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

No annotations are provided, so the description must disclose behavioral traits. It mentions downloading and extracting but omits critical details like network dependency, file overwrite behavior, storage location, or time expectations. This is insufficient for a mutation tool.

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 brief and front-loaded, with a clear breakdown of arguments. It avoids unnecessary words, though the formatting of arg descriptions could be more structured. Overall efficient.

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?

For a tool with 3 parameters, no output schema, and no annotations, the description leaves significant gaps. It does not explain the return value, side effects (e.g., file creation), or the role of the destination parameter. The tool's complexity requires more detail.

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 coverage is 0%, so the description adds value by providing examples for asset_id and variant. However, it completely ignores the destination parameter, leaving its purpose unclear. The examples are helpful but not comprehensive.

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 uses specific verbs 'Scarica ed estrae' (download and extract) and identifies the resource as ambientCG assets, clearly distinguishing it from siblings like preset_download_url (URL-based) and preset_extract_archive (archive extraction).

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 usage for ambientCG assets but provides no explicit guidance on when to use this tool versus alternatives like preset_search_ambientcg or preset_download_polyhaven. No exclusions or prerequisites are given.

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