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 disclose behavioral traits. It mentions 'optional filtering' and returns a 'formatted list,' but omits details like read-only nature, error handling, pagination, or API rate limits. The description is insufficient for a search tool.

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: a one-sentence purpose followed by a clear bullet list of parameters. It is front-loaded with the main action and avoids unnecessary fluff. Every sentence adds value.

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 covers the search function and all parameters, but lacks detail on the return value ('formatted list' is vague) and does not address error cases or rate limits. With no output schema, more detail on result structure would be expected for full 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 must compensate. It explains each parameter: 'query' as search text, 'categories' as optional comma-separated list, 'count' as max results with default 20, and 'downloadable' as filter with default true. This adds meaning beyond the schema's bare titles, though it could be more specific (e.g., valid categories).

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 with optional filtering,' specifying both the action (search) and the resource (Sketchfab models). This distinguishes it from sibling tools like 'download_sketchfab_model' and 'get_sketchfab_status.'

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, such as when to prefer searching versus downloading or using other context scripts. It lacks explicit context or exclusions.

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