Api privacy personal data destroy

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description frames the operation as viewing/editing, directly contradicting the destructive write semantics. For a deletion tool the description should warn that the record is permanently removed; instead it implies a safe read/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?

A single short sentence, but it is generic boilerplate that provides no front-loaded information about the actual destroy operation. Brevity here reflects under-specification rather than efficiency.

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, single-parameter deletion tool with no output schema, the description omits the target resource semantics, irreversibility, lookups/duplicate consumers of a personal data record, and confirmation requirements. An agent could not safely call this based on the description alone.

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?

One required parameter (id) with 0% schema description coverage, and the description says nothing about what the id identifies or what format it takes. The description must compensate for the coverage gap for a destructive operation but adds no parameter meaning at all.

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 personal data to be 'viewed or edited', which conflicts with the tool name (destroy) and true purpose of deleting a personal data record. It names a resource but the stated verb set is generic DRF boilerplate that does not distinguish this tool from the sibling list/retrieve/update operations.

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 the many sibling personal_data endpoints (retrieve, list, update, partial_update). No prerequisites, no warning about irreversible deletion, no mention of the required id.

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