openai_list_models

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

The description does not disclose any behavioral traits such as authentication requirements, rate limits, or whether the operation is read-only. Since annotations are absent, the description carries the full burden, yet it provides minimal insight. The agent might be surprised by the required api_key parameter.

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 sentence with no excess words. However, it may be too concise to be helpful, lacking structure or detailed information.

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?

The tool has no output schema, and the description does not specify what the response contains (e.g., list of model IDs, names, or metadata). The agent is left without key context needed to use the output effectively. For a list tool, this is a significant gap.

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 only parameter is 'api_key' (required), and the schema has 0% description coverage. The description does not explain the parameter's purpose, format, or constraints. While the parameter name is self-explanatory, the description adds no value beyond the schema.

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 'List all OpenAI models available to the account.' clearly specifies the action (list) and the resource (OpenAI models). It distinguishes the scope (all models available to the account) from potential siblings that list models for other providers. However, it does not differentiate from other list_models tools except by naming OpenAI, which is already in the name.

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 is provided on when to use this tool versus alternatives (e.g., openai_chat_completion) or when not to use it. There is no mention of prerequisites or context. The agent must infer usage from the name alone.

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