search_sketchfab_models

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool returns a formatted list but does not explicitly state that it is a read-only/non-destructive operation, nor does it disclose rate limits, data source freshness, or any side effects.

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, using a clear list format for parameters and a short statement about the return value. It front-loads the main action and avoids unnecessary detail. A minor improvement would be to use markdown for better readability.

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 the tool's moderate complexity (4 parameters, 1 required) and the presence of an output schema, the description adequately covers the essentials. It explains parameters and the return format. However, it could mention sorting or pagination details for 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?

The input schema has 0% description coverage, so the description adds significant value by explaining each parameter's purpose: query (text to search), categories (comma-separated list), count (max results, default 20), downloadable (only downloadable models, default True). This compensates fully for the schema's lack of descriptions.

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,' which is a specific verb+resource combination. It distinguishes itself 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 does not provide guidance on when to use this tool over alternatives, mention prerequisites, or specify contexts where it is appropriate or inappropriate. It only describes the tool's functionality without usage boundaries.

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