tdarr_delete_job_reports

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

The description discloses that deletion affects both database and disk, providing key behavioral context. However, it does not specify whether the operation is irreversible, what happens if filters match no records, or any confirmation steps. With no annotations, more details would be beneficial.

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, clear sentence that conveys the essential information without any filler. It is front-loaded and efficient.

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?

For a delete tool with one optional parameter and no output schema, the description covers the core action and scope. It does not specify behavior when no filters are provided (delete all? error?), which leaves a gap. Overall, it is fairly complete but could be slightly more explicit about default behavior.

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 describes the 'filters' parameter as an optional array of filter objects. The description adds 'multiple job reports' and 'with optional filters' but does not explain the structure or purpose of filter objects. Since schema coverage is 100%, the description adds minimal 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 clearly states the action ('Delete'), the target ('multiple job reports'), and the scope ('from both database and disk'). It also mentions optional filters, distinguishing it from the singular sibling 'tdarr_delete_job_report'.

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 on when to use this tool versus alternatives like 'tdarr_delete_job_report' for single deletions. No mention of prerequisites or conditions. The description implies bulk deletion but does not clarify if filters are required or what happens when omitted.

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