sketchfab_search

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

Annotations already communicate readOnlyHint=true and openWorldHint=true, so the safety and external-world scope are covered. The description adds the 'downloadable' qualifier, which hints at the result focus, but it does not disclose pagination behavior, network reliance, or how results are structured.

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 front-loaded with the verb, containing no filler. However, it is so terse that it leaves meaningful details unstated, which prevents it from being excellent.

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?

For a search tool with four undocumented parameters and no output schema, the description is too thin. An agent would not know what the response looks like, how to set 'order', how cursor usage works, or how 'downloadable' affects results. The sibling context suggests a search-then-get/import pipeline, but the description does not make that connection.

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 for parameter meaning, but it names no parameters at all. While 'search', 'limit', and 'cursor' are somewhat self-explanatory, 'order' is undefined, and there is no guidance on how cursor pagination works or what values are valid.

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 states a clear verb and resource: 'Search downloadable Sketchfab models.' This distinguishes it from nearby siblings like sketchfab_get and sketchfab_import. However, it does not clarify what 'downloadable' means in terms of result filtering or what is returned.

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 usage is implied: this is the tool to call when searching for Sketchfab models. However, there is no explicit guidance on when to prefer it over store_search, my_assets_search, or when to follow up with sketchfab_get or sketchfab_import. The agent must infer the workflow.

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