delete_report

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, consistent with deletion. The description adds no further behavioral context (e.g., whether deletion is permanent, cascading effects, or required permissions).

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 two sentences but includes a superfluous first sentence about managing and getting reports, which is irrelevant to deletion. Could be condensed to a single clear sentence.

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 two parameters and no output schema, the description is adequate but marred by the misleading first clause. Missing details on prerequisites or effects, but not critically incomplete given the tool's straightforward nature.

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 50% schema description coverage, the description does not compensate. It fails to explain the 'id' parameter or clarify the purpose of 'customerContext,' which already has a good schema description. The description adds no value beyond the schema.

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 the tool 'Deletes the specified Cloud Analytics report,' clearly identifying the action and resource. However, the first sentence about 'Manage Cloud Analytics reports and get reports data' is misleading and suggests broader functionality not supported.

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 on when to use this tool versus other delete or report management tools. Among siblings, there are many delete operations and report-specific tools (create_report, update_report, list_reports), but no distinctions provided.

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