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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safe read-only profile is covered. The description adds useful behavioral context by detailing what the returned metadata includes (curation status, modelling approach, SBML format/version, publication data, contributor roles, ontology annotations) and notes the CC0/EMBL-EBI provenance. It does not cover rate limits or error behavior, but the bar is lower because rich annotations are present.

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 front-loaded with the primary action and resource, followed by a purposeful enumeration of return fields and a closing workflow/licence note. Each sentence earns its place; the second sentence is long but meaningfully specifies what 'full metadata' entails, so it is appropriately detailed rather than padded.

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 one-parameter, read-only tool with comprehensive annotations and an output schema, the description is complete: it states the target resource, how to obtain the required ID, what the result contains, and the data source/licence. Nothing an agent needs in order to call it correctly 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% and the schema already documents the BIOMD vs MODEL prefixes, length constraints, examples, and the instruction to obtain IDs from search results. The description's accession example ('BIOMD0000000001' for the Edelstein model) is illustrative but adds no semantic meaning beyond what the schema already provides, placing it at the baseline for high schema coverage.

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 ('Get full metadata for a specific BioModels mathematical model by accession ID') and grounds it with a concrete example ID and model. The enumerated return fields plus the explicit 'Use biomodels.model.search first' workflow clearly differentiate it from its siblings (files, latest, search), so an agent can tell them apart without inspecting schemas.

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 instructs the agent to call biomodels.model.search first to discover accession IDs, naming the alternative and the ordering of the workflow. There is no ambiguity about when this tool applies: once an accession ID is known, this is the tool for full metadata.

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