list_models

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world access. The description adds useful context that the read is offline and does not trigger downloads, clarifying there is no network side effect, though it does not elaborate on how catalog and disk state are merged.

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 front-loaded sentence with no wasted words. It immediately communicates the operation and the key no-download constraint.

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 a full input schema, an output schema, and strong read-only annotations, the description covers the essential behavior an agent needs: it reads local catalog/disk state without downloading. The main remaining gap is sibling routing guidance rather than call-correctness details.

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 all five parameters are already documented in the input schema. The description adds no additional parameter semantics, which is acceptable given the schema coverage but means it only meets the baseline.

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 read operation over the offline catalog and current disk state, which aligns with the list_models name. It also distinguishes itself from downloading workflows by saying 'without downloading,' though it does not explicitly differentiate from siblings like find_model or refresh_catalog.

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 phrase 'without downloading' implies this is for browsing local catalog/disk state without network activity. However, it does not explicitly say when to use this versus find_model, refresh_catalog, or download_model, leaving alternatives to inference.

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