delete_job_reports

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

With no annotations provided, the description carries full behavioral disclosure. It clearly warns that with no filters this deletes every report and instructs the agent to confirm with the user first. This goes beyond the literal word 'delete' and reveals the high-impact destructive nature of the 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?

Two tight sentences earn their place: the first states the action and endpoint, the second immediately surfaces the critical safety warning and mitigation. No fluff, and the most important information is front-loaded.

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 simple one-parameter tool with full schema coverage, the description covers the essential context: bulk operation, filter narrowing, all-reports risk, and user confirmation. It does not mention return values or irreversibility, but for this dangerously destructive operation the main safety context is sufficiently complete.

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 description coverage is 100%, so the schema already explains that filters select which reports to delete and that omitting them deletes all. The description adds 'pass filters to narrow it' but no additional type, format, or syntax meaning beyond what the schema provides, so baseline 3 is appropriate.

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 states a specific verb ('Delete'), a specific resource ('job reports'), and a clear scope ('in bulk'), and even includes the endpoint. 'Bulk' differentiates it from the singular sibling delete_job_report, so an agent can tell them apart.

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?

It gives clear operational guidance: pass filters to narrow deletion, omit filters to delete everything, and confirm with the user first. It does not explicitly name the singular delete_job_report as the alternative for deleting one report, but the 'in bulk' phrasing and dangerous no-filter behavior provide strong contextual guidance.

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