list_ai_models

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (results may vary unpredictably). The description adds no additional behavioral traits beyond what annotations provide. It does not contradict annotations. The description is neutral, so a score of 3 is appropriate.

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?

Description is a single sentence with no extra words. It is front-loaded with the action 'Search' and clearly states the resource. Every word is necessary.

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 that parameters are documented, annotations cover critical behavioral traits (read-only, open-world), and there is no output schema, the description is adequate. It explains the tool's purpose well, though it could mention that it returns a list of models or that results are filtered by the search and task parameters. Nonetheless, it is sufficient for an agent to understand basic usage.

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?

Input schema covers all 3 parameters (account_id, search, task) with descriptions. Since schema coverage is 100%, the description adds no extra meaning to parameters. Baseline is 3.

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 'Search the catalog of Workers AI models available to the account.' It specifies verb (search), resource (catalog of Workers AI models), and scope (available to the account). This distinguishes it from sibling tools like run_ai which runs a model, and other list tools which target different resources.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or that it should precede run_ai. The phrase 'search the catalog' implies discovery, but no explicit usage context is given.

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