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

readOnlyHint=true already establishes this as a safe read, so the description's main added value is that it returns model IDs intended for downstream generation tools. It does not disclose pagination/limit interaction or whether the result set is exhaustive, so the added context is modest.

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?

Three short sentences, front-loaded with the action and resource, then filters, then return value. No filler, though the middle sentence's filter list is loose ('and more').

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 readOnlyHint covering the safety profile, 100% schema coverage for all 8 optional params, and the description explaining what the call yields, an agent has enough to invoke it correctly. The absence of an output schema is partly offset by the description naming the returned model IDs.

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 the schema already documents all 8 parameters and the baseline is 3. The description's 'category (imagen, video, audio, llm, 3d)' actually mirrors the feature parameter's domain rather than the category parameter's values (stable_diffusion, flux, etc.), which introduces mild ambiguity instead of adding clarifying meaning.

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?

States a specific verb and resource ('List available AI models on the ModelsLab platform') and clarifies the value of the output ('model IDs that can be used with generation tools'). It does not explicitly distinguish itself from the sibling list-providers, leaving that differentiation to inference.

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 implies usage by noting the returned IDs feed generation tools, and it gestures at the available filters, but it never states when to prefer this tool over list-providers or how to chain it into a generation call. Usage is implied rather than instructed.

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