sketchfab_search

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

With no annotations and a one-line description, the tool's behavior is opaque. It does not disclose whether it performs network requests, what results are returned, potential errors, or any side effects.

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 a single, concise sentence with no unnecessary words. It is well-structured and immediately understandable.

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?

The description is minimal and provides no context about expected outputs, how to handle results, or relationship to other Sketchfab tools. Given the presence of an output schema, the description still leaves the tool's purpose and usage incomplete.

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 input schema has no descriptions, and the tool description does not elaborate on parameters. While 'query' and 'count' are intuitive, 'categories' and 'downloadable' lack format or meaning clarification.

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 'Search Sketchfab models' clearly states a specific action (search) and target resource (Sketchfab models). It distinguishes from sibling tools like polyhaven_search or sketchfab_download.

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 gives no guidance on when to use this tool versus similar siblings (e.g., local asset search, Poly Haven search, or downloading from Sketchfab). It does not mention whether it is for external network searches or how it fits into the workflow.

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