litellm_delete

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

The description explicitly marks the tool as 'destructive, irreversible', which is a key behavioral trait. However, it does not disclose any other side effects, permission requirements, or error behavior beyond the single example.

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 relatively short and front-loads the destructive nature. The example is helpful, though it could be more tightly structured. Unnecessary repetition of 'litellm_delete' could be removed.

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?

With no output schema and low schema coverage, the description should provide more context about return values, error handling, and complete parameter semantics. The current description lacks this completeness, making it insufficient for complex 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?

The input schema has 0% parameter description coverage, so the description must compensate. It mentions 'operation' and 'params' but only through a single example; it does not explain the structure of 'params' or specify valid operations beyond the hint to use 'help'. This leaves the agent with insufficient guidance for correct invocation.

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 deletes LiteLLM resources and mentions cache flushall, making the purpose concrete. However, it does not enumerate the specific resource types that can be deleted, leaving room for ambiguity.

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 explains how to list available operations with 'help' and provides an example call, which guides usage. But it does not differentiate from sibling tools like litellm_read or litellm_execute, missing a clear when-to-use vs alternatives.

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