search

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

With no annotations, the description carries full burden. It discloses that the tool supports filtering and cursor-based pagination, which are key behaviors. However, it omits details like rate limits or data freshness, but the provided info is sufficient 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?

Two sentences: first sentence defines purpose, second adds features. No redundant words. Front-loads key information. Every sentence earns its place.

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 6 parameters and no output schema, the description could explain the return format (e.g., list of models with pagination metadata). It mentions cursor-based pagination but does not describe the response structure. Adequate but leaves gaps for a fully autonomous agent.

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 100%, so baseline is 3. The description adds little beyond the schema: it restates that query searches name, description, and category (already in schema) and mentions filtering/pagination (already implied by parameters). No additional semantic 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 the tool's purpose: 'Search for models in the fal.ai gallery using free-text query across name, description, and category.' This is a specific verb ('Search') and resource ('models'), and it differentiates from siblings like 'find' or 'models' by detailing the search scope.

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 implies usage for searching models with free-text and filtering, but it does not explicitly state when to use this tool versus alternatives (e.g., 'find' or 'models'). No exclusions or prerequisites are mentioned, so guidance is minimal.

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