list_models

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

The description mentions only the action of listing, but with no annotations, the burden falls on the description. It does not explicitly state that the operation is read-only, non-destructive, or has any side effects. However, the simplicity of the tool (no parameters, no mutations) makes this minimally adequate.

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 a single, complete sentence that fully explains the tool's functionality without any unnecessary words. It is front-loaded and efficient.

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?

Given the tool has no parameters and an output schema exists, the description is mostly complete. However, it could provide more context about why listing model aliases is useful, especially in relation to sibling tools like ask_model. As it stands, it is adequate but not rich.

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 no parameters, so the schema is fully covered (100%). The description adds no parameter information, but none is needed. The baseline for zero-parameter tools is 4.

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?

Description clearly states that the tool lists all model aliases from a specific configuration file. The verb 'list' and resource 'model aliases' are precise, and the tool name'list_models' aligns with this purpose. Sibling tools have different actions (ask, critique, pick, reason), making this tool distinct.

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 provided on when to use this tool versus alternatives. Although sibling tools are conceptually different, the description does not offer any context for decision-making, such as prerequisites or typical use cases.

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