download_sketchfab_model

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: scaling to target_size, required parameters, and notes on access rights. It also mentions return value (message with import details). Missing details on error handling (e.g., model not found) but adequate for a download 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 concise with clear sections and bullet-point examples. It is well-structured but could be slightly more streamlined (e.g., combining scaling and examples). No wasted sentences.

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 no output schema, the description adequately covers return value (message with details) and input parameters. It mentions access rights and scaling behavior. It is complete enough for an agent to use this tool correctly, though additional information about error cases would be beneficial.

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%, but the description compensates well for required parameters: it explains uid as unique identifier and target_size with examples (e.g., chair: 1.0). However, the optional user_prompt parameter is not described, though it has a default value. The description adds significant meaning beyond the schema for the critical parameters.

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 'Download and import a Sketchfab model by its UID,' which is a specific verb (download and import) and resource (Sketchfab model). It distinguishes from sibling tools such as search_sketchfab_models, get_sketchfab_status, and get_sketchfab_model_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 explains that the model will be scaled based on target_size and lists required parameters. It implicitly indicates this tool is for downloading/importing, but does not explicitly exclude cases where alternatives (like preview) should be used. More explicit when-to-use and when-not-to-use guidance would improve clarity.

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