Delete Report

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

With destructiveHint=true already present in annotations, the description merely restates the action ('Delete') without adding any context such as irreversibility, cascading effects, or whether special permissions are required. It does not contradict annotations, but provides zero additional behavioral insight beyond the structured data.

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?

Single sentence, front-loaded with the action, and zero wasted words. 'Delete a generated report.' is an appropriately sized description for a simple deletion tool.

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 delete with one parameter and full schema coverage, the description is adequate but lacks any mention of side effects, return values, or lifecycle context (e.g., cannot delete a report being generated). The presence of destructiveHint and complete param schema raise it to the minimum viable level, but it could be more 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?

The input schema already describes report_id as 'The report ID to delete' with 100% coverage. The description adds no extra meaning about the parameter, so the baseline score of 3 applies.

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 verb 'Delete' and the resource 'generated report', which is specific and distinguishes it from sibling delete tools like delete_project and delete_graph. No ambiguity about what this tool does.

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 provides no guidance on when to use this tool or any exclusions/alternatives. There is no mention of prerequisites (e.g., report must exist) or that it should be used only for generated reports. Sibling tools like generate_report and get_report exist, but no comparative usage advice is given.

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