Reports Delete Saved Report

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds the generic warning 'This may delete, clear, reset, or otherwise remove data,' which offers some context about side effects but is vague and does not specify what data is affected or whether the action is permanent. It does not contradict the annotations.

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 short and front-loaded with the primary action. The second sentence is somewhat redundant with the annotations, but it is brief and adds a cautionary tone without bloating the text. It is appropriately concise overall.

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 tool with one required parameter and strong annotations, the description is mostly sufficient. However, the vague second sentence leaves ambiguity about what exactly gets removed or reset, and there is no mention of permanence or return behavior. The annotations fill the safety gap, but the description could be more explicit about the operation's effects.

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 67%: fields and output_mode have descriptions, while report_id does not. The tool description adds no parameter-level meaning, but report_id is self-explanatory and the other parameters are already well described in the schema. The baseline of 3 applies given the high schema coverage.

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 begins with a specific verb and resource: 'Delete saved report.' This clearly differentiates it from sibling tools like reports_get_saved_report, reports_create_saved_report, and reports_update_saved_report. The added warning sentence does not obscure the core purpose.

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 versus alternatives, no conditions or prerequisites, and no mention of irreversibility or when deletion is appropriate. Usage must be inferred entirely from the tool name and first sentence.

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