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. It only describes parameters and states 'Returns a formatted list of matching models.' It lacks details on ordering, rate limits, or whether results are from the entire Sketchfab site.

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 (one paragraph plus parameter list) and front-loaded with the core purpose. Every sentence adds value, though the final sentence about return format is somewhat redundant.

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 no output schema and moderate complexity, the description explains parameter behavior but lacks context on pagination, error handling, or result ordering. The missing 'user_prompt' parameter also reduces 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?

With 0% schema description coverage, the description compensates by explaining 4 of 5 parameters (query, categories, count, downloadable) with clear meaning. However, it omits the 'user_prompt' parameter, leaving it 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's purpose: 'Search for models on Sketchfab with optional filtering.' It uses a specific verb (search) and resource (models on Sketchfab), and distinguishes it from sibling tools like download_sketchfab_model and get_sketchfab_model_preview.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include other search functions (e.g., search_polyhaven_assets), but no when/when-not or conditions are mentioned.

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