search_sketchfab_models

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that a 'formatted list' is returned, but does not disclose whether this makes network calls, whether results are live, pagination behavior, error handling, or any rate limits or auth requirements.

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 core purpose, followed by a tidy parameter list and a one-line return summary. There is no filler or redundant elaboration; every line communicates useful information.

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 absence of an output schema and annotations, the description should more thoroughly explain the return format and any special search behavior. It also fails to document the user_prompt parameter, which is a clear gap in completeness for a moderately parameterized tool.

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 description adds meaningful semantics for four of the five parameters: query text, comma-separated categories, maximum count, and downloadable filter. However, it completely omits the user_prompt parameter that appears in the schema, so the semantic coverage is not complete.

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 opens with a specific action and resource: 'Search for models on Sketchfab with optional filtering.' This clearly distinguishes it from sibling tools like download_sketchfab_model and get_sketchfab_model_preview, which serve different purposes.

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 gives no explicit guidance on when to use this tool vs alternatives such as search_polyhaven_assets or download_sketchfab_model. Usage is only implied by the phrase 'Search for models on Sketchfab'; there are no context cues, exclusions, or alternative tool references.

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