Deleting a custom report

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

The description states the tool deletes a report, consistent with annotations (destructiveHint=true, readOnlyHint=false, idempotentHint=true). However, it adds no additional behavioral context beyond the annotations, such as irreversibility or cascading effects on subscriptions.

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 concise with two sentences. The first sentence repeats the title, but the second is precise. Could be more succinct by omitting the first sentence, but overall it is well-structured and not verbose.

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-by-ID operation with an output schema and clear annotations, the description is mostly complete. It fails to mention the confirm and dry_run parameters, but these are documented in the schema.

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 100%, so the schema already documents all three parameters. The description mentions 'specified by its ID' referring to report_id, but adds no further semantic value beyond what the schema provides.

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 exactly what the tool does: 'Deletes a custom report specified by its ID.' It clearly identifies the verb (delete) and resource (custom report), and distinguishes it from sibling tools like action1_create_report, action1_update_report, and action1_list_reports.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., needing the report ID) or situations where deletion should be avoided. The only hint is 'Perm: manage_reports,' but this does not constitute usage guidelines.

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