search_sketchfab_models

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

With no annotations, the description must fully disclose behavior. It states the return format (formatted list) but omits side effects, auth requirements, rate limits, or error handling. A search tool is typically read-only, but the description does not confirm this.

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 single-line purpose and a bulleted parameter list. It is front-loaded, but the parameter list could be more structured (e.g., using a table). Still, it avoids unnecessary verbosity.

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, 5 parameters (one undocumented in description), and no annotations, the description is incomplete. It does not cover return value details, error scenarios, or edge cases like empty results. The missing 'user_prompt' parameter limits 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 coverage is 0%, so the description should explain all parameters. It describes 4 of 5 parameters but misses 'user_prompt'. Explanations are minimal (e.g., 'text to search for' for query). No additional meaning beyond basic types.

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 distinguishes from sibling tools like search_polyhaven_assets (different platform) and download_sketchfab_model (different action).

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 implies usage for searching Sketchfab models but does not explicitly state when to use this tool over alternatives, nor does it provide when-not-to-use guidance. Context signals show siblings like search_polyhaven_assets, but no comparative guidance is given.

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