Api privacy processings destroy

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

Annotations declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, yet the description frames the tool as an export mixin. The description contradicts the structured safety signals and discloses nothing about irreversibility, cascading deletions, or required authorization.

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?

It is a single short sentence, so there is no bloat, but the content is entirely off-topic and consumes the only descriptive slot with irrelevant information. Brevity cannot compensate for being wrong.

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, open-world mutation tool with no output schema and zero schema documentation, the description should explain the target resource, deletion consequences, and permissions. It supplies none of this and instead misidentifies the 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?

Schema description coverage is 0% and the single required 'id' parameter is undocumented. The description adds no information about what the id identifies or its format, and instead talks about export formats that do not exist as parameters.

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 says 'Generic export mixin for CSV/XLSX exports', which describes an export capability rather than the delete operation the tool name and annotations indicate. An agent reading it would conclude this tool exports data, the opposite of a destroy endpoint. This is misleading rather than merely vague.

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 guidance about when to delete a privacy processing, what alternatives exist (e.g. the sibling list/update tools), or any preconditions such as required permissions. Worse, the stated use case (exporting CSV/XLSX) points the agent toward the wrong action entirely.

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