tdarr_delete_cache_file

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

No annotations are present, and the description only repeats the action without disclosing traits like irreversibility, required permissions, or side effects. The description fails to add behavioral context beyond the basic operation.

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 very concise at only three words, but it lacks necessary details that would justify its brevity. It is not front-loaded with critical 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?

Given the simplicity (one parameter, no output schema), the description is still inadequate. It should at least hint at the type of cache file or the consequences of deletion.

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 100%, with the parameter 'file' described as 'Cache file to delete'. The description adds no extra meaning beyond the schema, so it meets the baseline but provides no enhancement.

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 'Delete a cache file', specifying the verb and resource. However, it does not differentiate from sibling tool 'tdarr_delete_file' which might delete other file types, lacking specificity for an AI agent.

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 like 'tdarr_delete_file' or 'tdarr_delete_backup'. The description offers no context for selection.

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