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 fully covered. The description adds meaningful behavioral context beyond the annotations: it enumerates the file categories (primary SBML/CellML, auto-generated conversions, supplementary figures/scripts) and the exact metadata fields returned (MIME type, byte size, MD5/SHA-256 checksums, direct download URL). This gives the agent a concrete expectation of the response shape even without an output schema.

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, information-dense sentence that front-loads the core action ('List every file attached to a BioModels entry') and then packs the file categories, metadata fields, and workflow context into the rest. Every clause earns its place; there is no filler, repetition, or vague marketing language. The final sentence about being the step between finding and loading a model is a high-value routing cue, not padding.

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 read-only, idempotent list tool with a single well-documented parameter and no output schema, the description is complete. It tells the agent what files will be listed, what metadata will be returned, and where this tool fits in the workflow. The annotations cover safety and idempotency, and the schema covers the parameter. There is no meaningful gap that would prevent an agent from selecting and invoking this tool correctly.

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 single parameter model_id is documented with an example ('BIOMD0000000012'). The description reinforces the parameter's role by framing the tool as listing files for a BioModels entry, which makes it clear that model_id identifies the entry. The description adds a bit of context about what the ID refers to, but the schema already does the heavy lifting, so a 4 is appropriate rather than a 5.

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 every file attached to a BioModels entry') and enumerates exactly what is included (primary model, auto-generated conversions, supplementary files) and what metadata is returned (MIME type, byte size, checksums, download URL). It also distinguishes itself from the model-finding step by naming itself as the step between finding a model and loading it into a simulator, which separates it from sibling tools like biomodels_model and biomodels_search.

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 clearly implies when to use this tool: after finding a model and before loading it into a simulator. It does not explicitly name sibling alternatives or state when not to use it, but the workflow positioning ('This is the step between finding a model and actually loading it into a simulator') provides clear contextual guidance. A small deduction because it doesn't explicitly contrast with biomodels_model or biomodels_search.

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