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 known. The description adds value by detailing the returned content (SBML notes, curation status, modelling approach, etc.), which goes beyond the annotations. No contradictions found.

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, well-structured sentence that front-loads the action and id format, then lists the returned fields. It is thorough but not bloated; every element serves to inform the agent. Slightly long due to the field enumeration, but still efficient.

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?

With only one required parameter and no output schema, the description fully explains what the tool returns by listing all fields. It covers the essential behavior, including the id prefix convention and use cases. Nothing an agent needs 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 explains the model_id format with examples. The description repeats the BIOMD vs MODEL distinction, adding little beyond what the schema provides. It does not introduce new parameter semantics, so the baseline of 3 applies.

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 (fetch), a specific resource (one BioModels entry), and the identifier format (BIOMD…/MODEL…), distinguishing it from the sibling biomodels_search which presumably returns lists. It also enumerates the exact fields returned, leaving no ambiguity about scope.

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?

Explicit guidance is given: 'Use after biomodels_search, or when a paper cites a BIOMD accession.' This tells the agent when to invoke it and implies the sequencing with search. It does not explicitly mention alternatives like biomodels_files, but the primary context is clear.

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