list_models

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

The description explains that it returns a one-line summary for each model, but it does not elaborate on other behavioral aspects such as sorting, filtering, or authentication requirements. Since no annotations are provided, the description carries the full burden, and while sufficient, it lacks depth.

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 consists of two concise sentences. The first sentence states the action and result, and the second provides usage guidance. All words are meaningful and front-loaded.

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 or output schema, the description adequately covers its purpose and usage. It could be slightly enhanced by describing the output structure, but it is sufficiently complete for the agent to understand its role.

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 tool has zero parameters, so the baseline is 4. The description does not need to add parameter meaning beyond the schema, which is complete. No additional value is expected.

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's action ('List all Cockpit content models') and the resource ('collections & singletons'). It also distinguishes itself from siblings like describe_model (detailed view) and list_items (items within models) by providing an overview with one-line summaries.

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 phrase 'Start here to see what content exists' provides explicit guidance on when to use this tool: as an initial step for exploration. While it does not explicitly exclude other scenarios or mention alternatives, the context makes the usage clear.

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