chat_completion

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

There are no annotations, so the description must carry the burden of behavioral disclosure. It does not mention authentication requirements, rate limits, streaming behavior, whether the operation is read-only or has side effects, or the shape of the response. The only added behavioral detail is model support, which is static compatibility, not operational behavior.

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 composed of two short sentences with no extraneous vocabulary. It leads with the primary function and adds a brief note about model compatibility. While concise, it is perhaps too sparse to be fully informative, but this dimension focuses on lack of bloat.

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's moderate complexity (six parameters) and absence of annotations or output schema, the description is insufficiently complete. It doesn't explain return values, potential errors, or any operational caveats, leaving the agent to make assumptions. More behavioral context is needed for reliable invocation.

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 provides descriptions for all six parameters, achieving 100% coverage. The description itself does not elaborate on any parameter beyond what the schema already states; for instance, 'model' is described in the schema with examples. Thus, the description adds no additional semantic value over 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 clearly identifies the action ('Generate chat completions') and the platform ('LiteLLM'), providing a specific verb and resource. However, the presence of a sibling tool named 'completion' without any distinguishing commentary means it does not fully differentiate itself from similar tools.

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 offers no guidance on when to use this tool versus alternatives such as 'completion' or other model interaction tools. No usage scenarios, exclusions, or alternative references are provided, leaving the agent without direction for tool selection.

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