delete_custom_report

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the destructive profile is known. The description adds nothing beyond that: no statement that deletion is permanent/irreversible, no permission requirements, no note on whether schedules or report data referencing the report are affected. With annotations covering only the safety hint, this leaves meaningful behavioral gaps unaddressed.

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?

A single short sentence with zero padding, front-loaded verb. It is efficient, though arguably under-specified rather than truly concise.

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 destructive mutation tool with an undocumented required parameter and no usage guidance, the description is inadequate; the output schema relieves it of explaining return values, but the irreversibility and identifier semantics that an agent needs before committing are missing.

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 0% for the single parameter 'report_id', and the description offers no compensating detail about its format, source, or how to obtain it. The agent must infer the identifier entirely from the name.

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 clear verb+resource ('Delete a custom report'), but it essentially restates the tool name with no additional specificity. It gives no hint about scope (per-user vs enterprise-wide), which distinguishes nothing from siblings like delete_data_source. Minimum viable, nothing more.

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 when-to-use guidance, no prerequisites, and no mention of alternatives (e.g., should a report be unpublished or archived instead of deleted). The agent gets no criteria for choosing this tool over the many other destructive/list siblings.

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