search_models

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

No annotations are provided, so the description must carry full burden. It explains the zdr parameter's default behavior (server setting) but does not disclose other behavioral traits such as whether it returns multiple results, pagination, or error handling. The existence of an output schema may cover return format, but it is not visible here.

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 brief and front-loaded with the purpose. The arguments are listed clearly in a structured format. Every sentence adds value without 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 (two optional parameters, substring search) and the presence of an output schema, the description covers essential usage. It could mention whether results are deduplicated or if multiple matches are returned, but overall it is adequate.

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%, but the description adds meaning to both parameters: search is a substring filter on model identifiers, zdr filters by ZDR compatibility with a default from server setting. This compensates for the empty schema descriptions.

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: 'Find exact model identifiers.' It distinguishes itself from siblings by explicitly instructing to call this before completion or start_research, and by implying it's different from search_families and annotate_models.

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 gives explicit guidance: 'Always call this to verify a model ID before passing it to completion or start_research — do not guess IDs.' This tells the agent exactly when and why to use this tool, and warns against guessing.

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