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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints. The description adds valuable behavioral context beyond this: the sorted-by-last-update-descending ordering, the specific returned fields (accession IDs, names, format, dates, submitter, URL), and the curation/peer-validation process. This exceeds what annotations alone convey.

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 compact and front-loaded with the primary action and result. The extra detail about curation and ontology annotations is informative without being bloated, and the license/source line is a reasonable addition. Slightly verbose in the middle, but every sentence adds meaningful context.

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 simple parameter set (one optional limit), the presence of an output schema, and safe read-only annotations, the description fully covers what an agent needs: what is returned, the ordering, the curation semantics, and the intended discovery use case. Nothing critical is missing.

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% (the single 'limit' parameter is fully described with min/max/default). The description doesn't mention the parameter, but the schema already carries the full burden. Per the baseline rule for high schema coverage, a 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 opens with a specific verb and resource: 'List the most recently updated manually curated mathematical models in BioModels.' It clearly distinguishes this tool from the sibling search tool by focusing on recency and curated status, and further clarifies scope with the BIOMD prefix detail.

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?

It explicitly states the intended use: 'Use to discover newly added or recently revised biological models across all domains.' This gives the agent clear context for when to select this tool, though it does not mention exclusions or explicitly name sibling alternatives (e.g., biomodels.model.search).

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