search_sketchfab_models

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds that the tool returns a formatted list and that filtering is optional, but it doesn't disclose potential side effects (though likely none), sorting behavior, or any rate limits. The description adds some value beyond the schema but is not rich.

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 a clear one-line purpose statement followed by a list of parameters and their meanings. Every sentence adds value, and the structure is easy to scan.

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 covers the basic search functionality and parameter explanations, but it lacks information about the output format beyond 'formatted list', omits the user_prompt parameter, and provides no guidance on alternative tools. Given no output schema or annotations, more detail would be needed for full completeness.

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 explains the meanings of query, categories, count, and downloadable, including syntax (comma-separated list) and defaults. However, it omits the 'user_prompt' parameter entirely, leaving that parameter undocumented.

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 searches for models on Sketchfab, with a specific verb ('search') and resource ('models on Sketchfab'). It also indicates the outcome by noting it returns a formatted list, distinguishing it from other tools like download_sketchfab_model or search_polyhaven_assets.

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 explicit guidance on when to use this tool versus alternatives. It does not mention alternative tools for other asset sources (e.g., search_polyhaven_assets) or conditions where this tool is preferred.

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