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

No annotations are provided, so the description must disclose behavioral traits. It does mention cursor pagination, which is useful, but it does not state whether the operation is read-only, what the response shape is, or whether there are any side effects. The word 'catalog' implies read-only but is not explicit.

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?

The description is short and to the point, with the core purpose front-loaded and the pagination behavior stated right after. Every word earns its place, though the brevity leaves gaps in other dimensions.

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 listing tool with two optional parameters and no output schema, the description provides only the core concept and a pagination hint. It lacks information about return format, ordering, authentication, or how this tool relates to its siblings, which is insufficient for reliable selection and invocation.

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 50%: only the cursor parameter has a description. The description itself adds no parameter-specific meaning, and it does not explain how limit interacts with pagination or what values are appropriate. Since schema coverage is not high, the description should have compensated but did not.

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 clearly identifies the tool as a catalog of active models, which conveys a listing operation on a specific resource. It also mentions cursor pagination, adding precision. However, it does not explicitly differentiate this from sibling tools like models_search or models_get_pricing.

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?

No guidance is given about when to use models_list versus alternatives such as models_search or models_get_pricing. The description lacks exclusions, prerequisites, or contextual scenarios, leaving the agent to infer usage.

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