download_sketchfab_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 of behavioral disclosure. It names the action but does not reveal whether the download is asynchronous (especially relevant given status-polling siblings), what changes occur in the scene, or what happens on failure.

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 eight words with no filler, and the core identifier (UID) is front-loaded. Every word contributes meaning.

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 single-parameter tool, this is minimally sufficient to make a call, but the lack of any outcome or async guidance—especially when sibling status tools exist—leaves the agent uncertain about what happens after invocation. Some behavioral context is missing.

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 100%, and the schema already fully describes the uid parameter. The description adds no new semantic detail beyond restating 'by UID', so it meets the baseline but does not exceed it.

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 states a specific action verb ('Download and import'), the resource ('Sketchfab model'), and the identifying input ('UID'). It clearly distinguishes this from sibling tools like download_polyhaven_asset and search_sketchfab_models.

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 when a Sketchfab model UID is already known, which pairs naturally with search_sketchfab_models, but it never explicitly states when to prefer this over alternatives or mentions any exclusions. The context is clear but under-specified.

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