Search Fab assets

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that free assets are the default, which is a specific behavioral trait. No contradiction with annotations.

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 extremely concise (two sentences), but given the tool's complexity (19 parameters, 0% schema coverage), it is under-specified. Conciseness should not come at the expense of clarity; more detail on parameters and usage is needed.

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 19 parameters and no schema descriptions, the description fails to provide adequate context for the tool's capabilities. It does not mention pagination, filtering logic, or key use cases, despite an output schema being present. The description is too minimal for a search tool of this complexity.

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%, meaning no parameter descriptions exist. The tool description does not explain any of the 19 parameters (e.g., cursor, tags, channels). It only hints at priceMode via the 'free assets' default, which is insufficient for effective parameter use.

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 the tool searches public Fab marketplace listings and notes that free assets are returned by default, which distinguishes it from siblings like fab_get_asset (single asset) and fab_list_limited_time_free. However, it does not explicitly contrast with all siblings, so it slightly misses the top score.

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?

No guidance is provided on when to use this tool versus alternatives like fab_list_limited_time_free or fab_download_free_asset. The description implies default behavior (free assets) but does not explain context or exclusion criteria.

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