search_models

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

With no annotations, the description must disclose behavior. It only states search dimensions but omits whether the tool is read-only, requires authentication, has rate limits, or returns a list versus single item. No side effects or behavioral traits are mentioned.

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 a single sentence, which is concise, but the typo 'APIAny' and ambiguity reduce clarity. It could be more structured and accurate.

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?

The tool has 3 parameters and no output schema. The description fails to explain the return format, pagination (limit behavior), or how to effectively use the search. It leaves significant gaps for an agent to invoke correctly.

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 parameter descriptions are empty (0% coverage). The description hints that 'query' is for natural-language text and 'type' for modality, which adds some meaning. However, it also introduces 'provider' and 'capability' which are not in the schema, causing confusion. The 'limit' parameter is not addressed.

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 identifies the tool as searching models by natural-language text, provider, modality, or capability, but contains a typo ("APIAny") and overpromises search dimensions not present in the schema (provider, capability). The core purpose is vaguely clear but lacks precision.

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 over siblings like list_models or get_model. The description gives no context about appropriate use cases or exclusions.

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