Api privacy purposes destroy

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description says the endpoint is for viewing or editing purposes and never mentions deletion, irreversibility, or destruction of an existing record. This creates an annotation contradiction: the structured metadata says destructive, while the prose frames it as view/edit.

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 only one short sentence, so it is concise, but the sentence is generic boilerplate and does not front-load the destructive action. Conciseness cannot rescue a sentence that actively misdirects.

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 endpoint with no output schema and an undocumented required id, the description should at minimum explain deletion semantics, required permissions, and consequences. It instead supplies only a generic 'viewed or edited' statement, leaving the agent without the information needed to invoke it correctly.

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?

The single required parameter is 'id' with 0% schema description coverage, and the description provides no explanation of what the id represents or that it must identify the purpose to delete. The description must compensate for the schema gap but does not.

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 the endpoint allows purposes to be 'viewed or edited,' which is misleading for a tool whose name and annotations identify it as a destroy/delete endpoint. It does not state that the operation deletes a privacy purpose, so the agent cannot rely on it to distinguish this tool from retrieve or update siblings.

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 given about when deletion should be used, what prerequisites exist, or how it differs from the sibling privacy_purposes_retrieve/update/list tools. The description instead implies view/edit usage, which is the opposite of the intended destructive action.

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