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

With no annotations provided, the description carries the full burden. It discloses return values (rank, Elo, URL) and the default fusion behavior across reasoning-effort settings, which adds meaningful context beyond the schema. However, it does not mention any potential limitations or side effects, but for a read-only search this is acceptable.

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 three short sentences that front-load the main purpose, then enumerate return values and default behavior. Every sentence adds information and there is no fluff or repetition.

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?

For a search tool with three well-documented parameters and no output schema, the description covers the essential aspects: what it does, what it returns, and its default variant handling. It lacks guidance on when to use it relative to siblings, but the tool is simple enough that this is a minor gap.

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%, so all three parameters (query, limit, include_variants) are already documented. The description adds only minor context (e.g., 'fused across reasoning-effort settings') that is essentially a paraphrase of the include_variants schema description, so it provides little additional meaning.

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 uses a specific verb ('Find') and resource ('ranked models'), and specifies the search dimensions (partial name or provider). It clearly distinguishes from sibling tools like get_leaderboard and search_benchmarks by focusing on model search.

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 use when searching for models by name or provider but provides no explicit guidance on when to prefer this over sibling tools like get_leaderboard or get_model. No exclusions or alternative tool references are given, so usage context remains implicit.

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