delete_report

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

With no annotations, the description carries the full disclosure burden. It clearly states the action is irreversible ('no per-object undo'), that it deletes the report and its content, and it documents possible return statuses (deleted, not_found, delete_failed). This goes beyond a simple mutation warning, though it does not cover permission requirements.

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 compact and well-structured: the primary purpose is stated in the first sentence, followed by a useful caveat about undo and the return format. Every sentence earns its place with no redundancy.

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?

The tool has a single simple parameter, full schema coverage, an output schema, and a description that covers purpose, irreversibility, and return values. There are no missing behavioral or usage details needed for an agent to safely invoke it.

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 provides 100% coverage with a clear description for the only parameter, report_id. The tool description adds no additional parameter-level meaning, so the baseline of 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 opens with a specific verb and resource: 'Delete a Visual Analytics report and its content.' This clearly distinguishes delete_report from sibling tools like get_report, list_reports, create_report, and copy_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?

It explains when this tool is the appropriate choice by noting there is no per-object undo and positioning deletion as the way to discard unwanted reports. It also mentions copying first as a safety alternative, though it does not explicitly name sibling tools or rule out other scenarios.

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