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. It discloses that the model will be scaled to target_size, that it downloads and imports, and that access rights are required. This provides good transparency for the core behavior. However, it does not describe what happens to existing objects in the scene or whether the import is reversible.

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 structured with a summary sentence followed by a parameter section with bullet points. The examples add clarity without being verbose. Each sentence contributes meaning. Slight room for improvement by integrating user_prompt explanation.

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 complexity of importing a 3D model, the description covers the main action and scaling but lacks information on scene impact (e.g., will it add to collection or replace selection). It also does not mention any prerequisites beyond access rights. The return value is vaguely described as 'a message with import details'. A more complete description would address these gaps.

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 adequately explains uid and target_size with examples, but ignores user_prompt. The parameter list in the description only covers two of three parameters, leaving user_prompt undocumented. This is a moderate gap.

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 verb (download and import), the resource (Sketchfab model), and the method (by UID). It also mentions scaling to target_size. This distinguishes it from siblings like search_sketchfab_models (searching) and get_sketchfab_model_preview (previewing), making the purpose unambiguous.

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 you have a Sketchfab UID and want a model imported at a specific size, but it does not explicitly state when to use this tool over alternatives like download_polyhaven_asset or generate_hyper3d_model_via_text. There is no when-not-to-use guidance or exclusion criteria, leaving some ambiguity for the AI agent.

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