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

No annotations are provided, so the description carries the full burden of disclosing behavior. It discloses no read-only guarantee, output format, side effects, or catalog semantics beyond a vague URL reference.

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 text is short, but the first sentence is a tautology and the second is an external URL reference that does not explain the tool. Compactness is not useful when the content is uninformative.

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?

Even for a zero-parameter tool, there is no output schema or annotation coverage, so the description must at least clarify what the returned model list contains and how it should be used. It merely names an external catalog, leaving the agent unable to predict the tool's results.

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 input schema declares zero parameters and schema description coverage is 100%, so the baseline is 4. The description adds no parameter-level detail, but with no declared parameters there are no semantics that require clarification.

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 begins by restating the tool name ('MCP-Agents tool list_models') and then points to a live catalog URL without ever stating that the tool lists or retrieves models. It gives no clear verb+resource definition and does not distinguish this from sibling tools like list_vertical_plugins or get_model_policy.

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 guidance on when to use this tool, what it returns, or how it relates to alternatives such as list_pricing, list_vertical_plugins, or get_model_policy. An agent is given no routing information.

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