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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description contributes genuinely useful domain context that annotations cannot — currency (rubles) and pricing unit (per 1M input/output tokens) — but it does not say whether all models are returned by default or how the result is shaped.

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?

It is a single short sentence with zero filler, and the most important detail (what is priced and in what unit) is front-loaded. It is arguably over-terse, omitting a verb, but nothing is wasted.

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 low-complexity read-only lookup with full schema coverage and clear annotations, the description covers the essentials. However, with no output schema, it never indicates that the result is a list of models with input/output price fields, nor whether an empty query returns everything — a gap an agent would notice at call time.

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 single 'query' parameter is fully documented in the schema (100% coverage) as an optional name filter, so the schema already does the work. The description adds nothing about matching semantics (substring vs exact, case sensitivity), 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?

The description names a specific resource — IRI Gateway model prices in rubles per 1M input and output tokens — so an agent knows exactly what data it returns. It lacks an explicit verb (no 'get/return') and never contrasts itself with the neighboring search_models or get_model_rating tools, so sibling differentiation rests entirely on the name.

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 guidance at all: nothing says to call this before cost estimation, nor when to prefer it over search_models or get_model_rating. The only filterable behavior is implied by the schema, not the description.

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