sketchfab_download

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

No annotations are present, so the description carries the full burden. It discloses the API token requirement, which is a behavioral prerequisite. However, it does not mention whether the import creates a new object, overwrites existing ones, or what happens on failure (e.g., invalid uid, network errors). The description only covers the token setup, leaving other behavioral aspects unspecified.

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 extremely concise: two short sentences that front-load the main action (download and import) and then add the token requirement. Every word serves a purpose, with no filler or redundancy. It is appropriately sized for a tool with a single parameter.

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 has one parameter with no schema description and no output schema, the description is incomplete. It omits critical context about the 'uid' parameter, how to find it (e.g., via sketchfab_search), and what the operation returns or any side effects. The token prerequisite is mentioned, but for a tool that interacts with an external service, more context about failure modes and expected outcomes is needed.

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?

The schema has one required parameter 'uid' with zero schema description coverage. The tool description does not explain what 'uid' represents (likely the Sketchfab model identifier) or how to obtain it. With 0% coverage, the description must compensate, but it fails to provide any parameter semantics, making it impossible for an agent to correctly populate the field without external knowledge.

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 tool downloads a Sketchfab model in glb format and imports it. This is a specific verb+resource action that distinguishes it from siblings like sketchfab_search (which searches) and polyhaven_download (which downloads from Poly Haven). The main purpose is 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 mentions the prerequisite of an API token (in plugin preferences or environment variable), which is a necessary setup step. However, it does not explicitly compare with alternatives or specify when to use this tool versus sketchfab_search (to find models) or import_file. No exclusions or when-not-to-use guidance is provided.

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