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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it explains the return format (accession IDs with BIOMD vs MODEL prefixes), the scope of the repository, and the curation status filter semantics. It doesn't mention pagination behavior beyond the offset parameter, but the schema covers that.

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 well-structured and information-dense without being bloated. It front-loads the core purpose, then provides repository context, return value details, and filtering guidance. The only minor issue is that some repository background (hosted by EMBL-EBI, CC0 license) is useful but not essential for calling the tool.

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 description is complete for a search tool: it covers what the tool does, what it returns, and how to filter. The output schema exists, so return values are documented. The only gap is that it doesn't explicitly state when to prefer this over biomodels.model.latest or biomodels.model.detail, but the sibling names make this reasonably clear.

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 the schema already documents all four parameters thoroughly. The description adds some value by explaining the BIOMD/MODEL prefix distinction and curation status meaning, but it doesn't add significant new parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb ('Search') and resource ('BioModels repository'), and clearly distinguishes this tool from siblings like biomodels.model.detail, biomodels.model.files, and biomodels.model.latest by focusing on search across the repository. It also explains what the repository contains and what the search returns.

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 provides clear context on when to use this tool (searching for models by keyword) and mentions filtering by curation status. It doesn't explicitly name alternatives or exclusions, but the sibling names (detail, files, latest) make the distinction inferable. The curation_status parameter description adds practical guidance on when to use it.

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