list_models

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

With no annotations, the description carries the burden of behavioral disclosure. It does add meaningful context by saying 'live' and warning that 'Catalog presence does not prove execution readiness.' However, it does not explicitly state that listing is read-only, mention authentication needs, or disclose rate limits or pagination behavior, which are relevant for a tool with no 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?

The description is two tight sentences with no filler. The main action is front-loaded, and the caveat about execution readiness is a valuable second sentence that earns its place without bloating the text.

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?

This is a low-complexity tool with one optional parameter and no output schema. The description explains what the entries identify and adds an important limitation. It does not detail the response format further, but for a simple catalog list the description covers the essentials an agent needs.

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 100%, so the single optional provider parameter is already fully documented in the schema. The description does not elaborate on the parameter's behavior, such as exact supported values or filtering semantics, but it is not required to compensate for a coverage gap.

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 uses a specific verb and resource: 'List the live APIClaw model catalog.' It also specifies what entries contain (owner, serving source, gateway endpoint), which clearly distinguishes this from sibling tools like discover_apis or list_categories. The added caveat about execution readiness reinforces what this tool does and does not provide.

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 description gives useful context: it is a catalog listing, not an execution readiness check. However, it does not explicitly name alternatives or state when to prefer this over related tools like discover_apis or get_api_details, leaving the agent to infer the selection logic.

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