list_models

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

With no annotations provided, the description carries the full transparency burden and does well by disclosing that the tool does not call the Cloudflare API, works without credentials, and returns a catalog with model roles. It lacks details about exact return formatting, but the absence of an output schema is partially compensated by the clear catalog description.

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 three sentences with no filler. It front-loads the core purpose, then gives usage guidance, then adds credential/API behavior context—each sentence earns its place.

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, parameterless listing tool with no output schema, the description fully covers what it returns, when to use it, and its external behavior. Nothing essential is missing given the tool's low complexity and rich sibling context.

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 correctly implies the tool requires no input and instead focuses on its output purpose, which is sufficient for a no-parameter discovery tool.

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 ('List') and resource ('Cloudflare Workers AI models supported by this server'), clearly distinguishing this discovery tool from the execution-oriented siblings chat_completion, embed_text, and generate_image. It also states the exact deliverable: a complete catalog of chat, embedding, and image models with their roles.

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 explicitly tells the agent when to use the tool: 'before calling chat_completion, embed_text, or generate_image'. It also clarifies that no credentials are needed and that no Cloudflare API call is made, preventing unnecessary setup or external calls.

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