download_sketchfab_model

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

With no annotations, the description carries the full burden. It discloses key behaviors: scaling to target_size, returning import details (object names, dimensions, bounding box), and the requirement that the model must be downloadable with proper access. It does not mention scene modification side effects or error handling, but for an import tool, this is reasonably transparent.

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 well-structured with a clear opening statement, a scaling note, a parameter list with examples, and return info. The examples for target_size are valuable despite adding length. It is concise enough while providing necessary details, with no fluff.

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 tool's moderate complexity (3 params, scaling, import details), the description covers the essential aspects: what it does, scaling behavior, return message, and access requirements. It misses the user_prompt param and doesn't discuss error scenarios, but for an import tool with no output schema, it is adequately complete.

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 thoroughly explains uid and target_size, including detailed examples for target_size. However, it completely omits the user_prompt parameter (present in the schema), leaving a gap. Since not all parameters are described, it only partially compensates for the missing schema descriptions.

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 action: 'Download and import a Sketchfab model by its UID.' It specifies the verb (download/import), the resource (Sketchfab model), and the key identifier (UID). It also mentions scaling behavior, which distinguishes it from sibling tools like search or preview.

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 (you need a UID and want to import a model) but does not explicitly compare to alternatives such as search_sketchfab_models or get_sketchfab_model_preview. It does provide context about scaling and access rights, but it lacks an explicit 'use this when you have a UID' or 'use search to find UIDs' guidance.

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