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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description adds nothing beyond that: it does not say whether deletion is permanent, whether it requires specific permissions, or what happens if the report is already processed. The opaque 'Internal.' tag conveys no actionable information.

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 verb and ownership constraint up front; no padding. The unexplained 'Internal.' prefix is a small waste of the limited space available.

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 one-parameter destructive tool with annotations covering the safety signal, the definition is minimally adequate. It omits consequences of deletion, permission requirements, and any hint of what 'Internal' restricts, leaving real gaps for a destructive operation.

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?

With a single parameter at 100% schema description coverage, the schema already documents report_id as the UUID of the report to delete. The description adds no format, ownership, or validation detail beyond that baseline.

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?

States a specific verb and resource: 'Delete a report'. However, it does not distinguish this from adjacent siblings such as update_report_status, send_report, or list_my_reports, and the leading 'Internal.' is unexplained rather than clarifying.

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 phrase 'a report you submitted' implies an ownership precondition, which is the only usage guidance given. There is no statement on when to delete versus update status or use other report tools, and no mention of confirmation or prerequisites.

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