download_sketchfab_model

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

Partially describes scaling behavior ('Scales to target_size') with examples, but omits critical traits like whether the model is imported into the current scene, what happens on duplicate UIDs, error handling, or blocking behavior. With no annotations, the description carries full burden and falls short.

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?

Extremely concise: one sentence plus inline examples. No wasted words, and the examples are directly relevant. Front-loads the key purpose and scaling behavior.

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?

Despite low complexity (2 params, no output schema), the description omits what the tool returns (e.g., import status, object name) and side effects (e.g., scene modification). The scaling examples are helpful but overall incomplete for a download/import operation.

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?

Adds context that 'uid' is a Sketchfab identifier and 'target_size' is the largest dimension in meters, with realistic examples. This goes beyond the schema (which has only param names/types), but does not specify uid format or allowed ranges.

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?

Clearly states 'Download and import a Sketchfab model' with scaling to target_size. Distinguishes from sibling download tools like download_polyhaven_asset or import_generated_asset by specifying the source (Sketchfab) and scaling behavior.

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?

No guidance on when to use this tool versus searching/downloading from other sources (e.g., search_sketchfab_models first) or handling prerequisites like model UID. Lacks exclusions or context for alternatives.

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