list_models

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only asserts that a list is returned. It does not state that the operation is read-only and side-effect free, whether results reflect the account's entitlements or a static catalog, whether the call is paginated or rate-limited, or what a returned item contains.

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?

A single front-loaded sentence with no filler, which is appropriate for a trivial zero-argument tool. The reference to the raw HTTP endpoint is marginally useful for traceability but adds no decision-relevant information for an agent.

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 no-argument list tool this is nearly sufficient, and the simple shape limits how much the description must carry. However, there is no output schema, and the description never indicates what identifying fields a model record exposes, which is the one thing an agent needs in order to use the results downstream.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema is consistent with the description's claim that this is an unfiltered listing.

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 a specific verb and resource ('List models') and ties it to the upstream endpoint GET /v1/models, so an agent knows exactly what is being enumerated. It does not explicitly distinguish itself from catalog-style siblings such as list_voices or list_music_finetunes, but the resource noun is unambiguous.

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?

There is no guidance on when to call this versus alternatives, nor any prerequisite or follow-up context. The description states only what the tool returns, leaving the agent to infer that it is a discovery call used to obtain model identifiers before a generation request.

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