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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. What the description adds is the return shape — far more useful than repeating 'read-only' — but it does not say whether the catalog is paginated, whether the list is exhaustive, or how 'how many machines fit each' is derived. With annotations doing the behavioral work, a 3 is right.

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?

One sentence, front-loaded with the resource, then a compact enumeration of returned fields. There is no filler, no restated title, and no marketing language. Every clause conveys a distinct field the agent will receive.

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 no output schema, the description carries the burden of describing return values, and it largely does so by listing the fields. That is sufficient for a zero-parameter read tool. Minor residual gaps: it does not clarify pagination, ordering, or what 'how many machines fit each' means quantitatively.

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?

The tool takes zero parameters, so schema coverage is trivially 100% and there is no parameter meaning to add. Baseline 4 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 names the resource unambiguously — 'the open models we track' — and enumerates the attributes returned (id, size, memory at 4-bit/8-bit, machine fit counts, measured-speed count, page URL). Combined with the title 'List models', an agent knows exactly what this tool yields. It does not, however, distinguish itself from the sibling find_for_model, which is model-related, so a small differentiation gap remains.

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?

Usage is only implied: a zero-parameter enumeration of the model catalog naturally reads as 'call this to get the full list.' There is no explicit statement of when to prefer it over find_for_model or the other siblings, nor any exclusion such as 'use find_for_model when you want machines that can run a given model.' That is adequate but leaves routing to inference.

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