search_sketchfab_models

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

No annotations are provided, so the description must fully convey behavioral traits. It states 'Returns a formatted list' but does not disclose whether the tool is read-only, has side effects, handles pagination, or has any limitations. The name implies searching, but lack of explicit transparency is a gap.

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 purpose. The parameter list is formatted clearly with one line per parameter. No unnecessary sentences. However, the return description could be integrated more succinctly.

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 tool with 4 parameters and no output schema, the description covers the basic usage and return format. It explains the parameters sufficiently for a search tool. However, it lacks details on error handling, what 'formatted list' entails, or any constraints on categories. It is minimally viable but not comprehensive.

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%, and the description adds meaning to all parameters, e.g., 'query: Text to search for', 'categories: Optional comma-separated list', 'count: Maximum number of results', and 'downloadable: Whether to include only downloadable models'. Default values are noted. While not exhaustive, this significantly aids understanding beyond the schema titles.

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', providing a specific verb and resource. However, it does not explicitly distinguish from sibling tools like 'search_polyhaven_assets' or 'download_sketchfab_model', which could cause confusion about when to use this tool vs. others.

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 provides no guidance on when to use this tool versus alternatives. It does not specify that this tool is for searching only and that downloads should be performed with 'download_sketchfab_model'. No exclusions or prerequisites are mentioned.

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