search_sketchfab_models

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it 'Returns a formatted list' and gives parameter defaults, but does not mention network/API requirements, authentication, error handling, or explicitly confirm that it is a read-only operation. This is insufficient for an unannotated 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 and well-structured: a one-sentence purpose, a bulleted parameter list, and a return statement. It contains no extraneous words and 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 purpose, most parameters, and the return type, but omits the user_prompt parameter and does not discuss behavior for no results or error cases. With no output schema or annotations, more detail on edge cases and potential failure modes 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?

The schema has 0% description coverage, yet the description compensates by explaining query, categories, count, and downloadable with meanings and defaults. However, the user_prompt parameter is missing from the description and is not explained in the schema, which prevents a perfect score.

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 'Search for models on Sketchfab' with a specific verb and resource, distinguishing it from sibling tools like download_sketchfab_model and search_polyhaven_assets. It also mentions 'optional filtering' and the return of a formatted list, making the tool's function 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 gives clear context: it is the tool for searching Sketchfab models, with optional filters such as categories and downloadable. However, it does not explicitly provide exclusions or mention alternatives, like when to use search_polyhaven_assets or get_sketchfab_model_preview instead.

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