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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: the newest-first ordering and the per-item payload (slug, token limits, reasoning support), which matters because there is no output schema. Pagination behavior is left to the schema rather than described.

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; ordering, scope, and returned fields are packed in without redundancy.

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 full schema coverage, no output schema, and annotations carrying the safety profile, the description supplies the return-field content the agent otherwise could not know. Pagination is deferred entirely to the schema, which is a minor gap rather than a missing requirement.

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 limit, cursor, orgID, and modelProviderConfigID are fully documented structurally. The description adds only the implicit notion that results are scoped to one provider config; it does not clarify cursor/limit semantics beyond the schema, so the baseline 3 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?

States a specific verb ("Lists") plus resource and scope ("models configured under one model provider config"), which separates it from models_create/update/delete and model_providers_list. It stops short of explicitly naming the sibling it is not, so it lacks the active sibling differentiation that would earn a 5.

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 when-to-use / when-not-to-use guidance and no mention of neighboring tools such as model_providers_catalog or grant_models_list. The provider-config scoping is the only cue about appropriate use, which is thin given how many list-style siblings exist.

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