Search UnoRouter models

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

With no annotations provided, the description carries the burden and does well by noting the catalog is 'live', that :free models cost nothing, and that results are usable with specified clients. It does not mention rate limits or error behavior, but for a search tool it provides useful behavioral context.

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 two sentences, front-loaded with the main action and resource, and every sentence adds value—covering scope, cost, and return usage. No fluff or redundancy.

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 simplicity (3 optional parameters, no output schema) and solid parameter descriptions, the description adequately covers purpose, return values, and integration points. It could mention pagination but the schema's limit and default are documented, so completeness is high.

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 100% for all three parameters, so the description adds little beyond what the schema already provides. The mention of ':free' cost complements the free_only parameter, but this is not essential for understanding parameter semantics.

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 the live UnoRouter model catalog, a specific resource. It also explains what it returns (matching model IDs) and their usability, distinguishing it from a generic search tool.

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 when to use the tool (when you need model IDs for chat or any OpenAI-compatible client) but does not explicitly compare with sibling tools like get_pricing. It lacks clear 'when not to use' guidance, though the purpose is fairly evident.

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