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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral fact not in annotations: filtering, sorting, and pagination are performed server-side rather than client-side. It stops short of describing return shape or paging edge behavior.

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 wasted words; the capability list is compact and immediately readable. It is perhaps too terse to be a 5, since it trades away any differentiating or routing detail for brevity.

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 simple read-only, org-scoped listing tool with full schema coverage and annotations covering safety, the description supplies enough context to invoke it correctly. The absence of an output schema is a minor gap, but listing return shape is predictable and next_cursor is already described in the cursor parameter.

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% and each of the five parameters is documented in detail (glob syntax, sort enum, cursor, limit), so the schema carries the burden. The description only generically echoes filtering/sorting/pagination without adding syntax or constraints beyond the schema, matching the baseline 3.

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 (List) and resource (model provider configs) and enumerates the capabilities (filtering, sorting, pagination). It is clearly a collection endpoint rather than a single-resource get/create, though it doesn't explicitly name sibling tools like model_providers_get or model_providers_catalog for contrast.

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 listing intent is implied clearly by the name and description, and 'cursor pagination' hints at how to page. However, there is no explicit when-to-use guidance versus model_providers_get or models_list, and no statement of prerequisites beyond the schema's required orgID.

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