litellm_execute

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

No annotations provided, so description must carry full burden. Mentions 'reversible actions' but includes 'targeted cache delete', implying some irreversibility. Lacks details on side effects, permissions, rate limits, or error handling. Important behavioral traits are missing.

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?

Three concise sentences plus an example. First sentence immediately states purpose, second gives help mechanism, third example. No unnecessary words or repetition.

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 2 params, no output schema, and no annotations, the description covers the broad purpose and usage pattern but lacks information about return values, error handling, and a full list of operations. Adequate but leaves gaps.

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?

Schema coverage is 0%, so description must compensate. Describes 'operation' as a string that can be 'help' or an operation name, and 'params' as a JSON object. Provides an example. However, does not enumerate common operations or parameter structures beyond the example, leaving the agent dependent on calling help.

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 states specific verb+resource ('Execute reversible actions on LiteLLM resources') with concrete examples (block/unblock, key regenerate/reset, cache delete). Clearly distinguishes from siblings like litellm_read (read-only) and litellm_admin (administration).

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?

Provides explicit guidance to call with operation='help' to discover operations and an example invocation. Does not explicitly exclude alternatives or state when not to use, but sibling names and purpose make context clear.

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