search_sketchfab_models

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

With no annotations, the description must disclose behavioral traits, but it only mentions returning a formatted list. It does not address external API calls, rate limits, authentication, pagination, or how results are sorted. This leaves the agent uninformed about potential side effects or constraints.

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 compact and well-structured: a purpose sentence, a short parameter list, and a return line. It avoids redundancy and front-loads the essential purpose, making it easy to parse.

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 incomplete for a tool with five parameters and no output schema. It omits user_prompt, does not specify the structure of the formatted list, and lacks details like allowed category values or result fields. An agent cannot fully anticipate the tool's behavior or output.

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 description explains four of five parameters (query, categories, count, downloadable) with clear semantics and defaults, which is beneficial since the schema has no field descriptions. However, it omits the 'user_prompt' parameter entirely, leaving a significant gap in parameter understanding.

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 function: 'Search for models on Sketchfab with optional filtering.' The verb 'search' combined with the explicit platform 'Sketchfab' distinguishes it from sibling tools like search_polyhaven_assets and from Sketchfab-specific actions like download or 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. It does not mention conditions for preferring this over search_polyhaven_assets or other search/download tools. The description implies usage for finding Sketchfab models but lacks explicit direction.

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