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

Annotations already declare readOnlyHint=true and idempotentHint=true, which fully characterize this as a safe, repeatable read. The description adds that it reflects 'as GET /models returns them' and that the catalog is 'active' models, which adds minor scoping context but no auth, rate-limit, or freshness detail beyond the annotations.

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 or repetition. The embedded clauses ('as GET /models returns them', 'for the widget's model pickers') are compact, though slightly qualifier-heavy.

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?

The tool is simple (no params, no output schema) and the description covers what is returned, its scope, and the intended consumer. For such a low-complexity, annotation-backed read tool, this is nearly complete; only the return shape and any update cadence are unspecified, which is acceptable.

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?

There are zero parameters, so the schema needs no compensation and the baseline is 4. The description correctly implies that no filtering or query options exist, matching the empty parameter object.

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 catalog), naming returned content: active AI models with capabilities and pricing rules. It is clearly distinguishable from the many list_* siblings by its subject matter, though it doesn't contrast against an obvious direct alternative.

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 phrase 'for the widget's model pickers' implies the consumer context, giving some sense of when it matters. However, there is no explicit when-to-use/when-not guidance and no named alternative among the siblings.

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