openai_list_models

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

With no annotations, the description alone should disclose behavior. It implies a read-only operation but does not detail authentication beyond api_key, rate limits, or pagination. Basic transparency is present but incomplete.

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, clear sentence with no extraneous words. It is optimally concise for a simple list operation.

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 no annotations or output schema, the description is minimally adequate: it states the function and scope. However, it could be more complete by hinting at the response format (model IDs vs objects) or that it only returns accessible models.

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 schema has 0% description coverage for the single parameter (api_key). The description adds no semantics about the api_key, leaving the agent to infer its purpose from the schema alone. A better description would clarify how the key is used.

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 states the tool lists all OpenAI models available to the account. It is specific about the resource (models) and action (list), and among OpenAI siblings it is distinct as the only listing tool.

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 on when to use this tool versus alternatives (e.g., checking model availability before chat completion). There is no mention of usage context or exclusions.

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