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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuinely new context by disclosing that approval requirements are org-configurable and that business workflow approvals always apply, but it never says whether the delete is permanent, what happens to reports in use, or what error occurs when approval blocks the call.

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 short sentences with the action front-loaded and no padding. The approval caveat is somewhat tangential to the tool's mechanics but is compactly expressed.

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?

With an output schema present, return values need no explanation, and safety hints are carried by annotations. Still, for a destructive single-parameter mutation, the description omits whether deletion is irreversible, whether approval must be granted before or after the call, and whether the tool is gated by the approval flow it describes.

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?

Only one parameter exists and the schema fully specifies its format (uuid), pattern, and required status, so the baseline of 3 applies. The description adds nothing about the id — it doesn't clarify whether it is the saved report's id or a report instance id — leaving that inference to the schema alone.

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 saved report'), which is unambiguous against siblings like update_saved_report or get_saved_report. It doesn't explicitly differentiate from those siblings, but the verb 'delete' does most of that work on its own.

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?

There is no statement of when to use this tool versus get_saved_report, list_saved_reports, or update_saved_report, and no prerequisites or exclusions are given. The approval sentence describes governance overhead rather than selection guidance, so an agent gains no routing help from it.

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