search_sketchfab_models

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

No annotations are provided, so the description must disclose behaviors. It only lists parameters and does not mention what the tool returns (e.g., list of model metadata), rate limits, or that it requires network access. Minimal behavioral disclosure.

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 short with three sentences, front-loading the main purpose. However, it lacks structure (e.g., bullet points) and omits the fourth parameter. Conciseness comes at the cost of completeness.

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?

With no output schema, the description should explain return values. It doesn't. It also ignores the 'categories' parameter. Given the tool's role in a larger workflow (search then download), the description should connect to subsequent steps. It is incomplete for the context.

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 description should compensate. It mentions three parameters (query, count, downloadable) but omits 'categories' and does not explain their meaning or constraints. The schema already provides defaults and types; the description adds little value.

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 Sketchfab for 3D models,' identifying the action and resource. It distinguishes from siblings like 'download_sketchfab_model' and 'get_sketchfab_model_preview' by focusing on discovery. However, it does not explicitly differentiate from other search tools like 'search_polyhaven_assets'.

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 a basic when-to-use: search for 3D models. But it lacks guidance on when not to use (e.g., for direct download) and does not mention alternatives or prerequisites. The usage context is implied but not explicit.

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