Api privacy data recipients 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 lets records be "viewed or edited" and never mentions permanent deletion, cascading effects, or permission requirements. For a destructive tool, the description actively undercuts the safety signal carried by the annotations.

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 with no padding, so it is concise, but the content is generic boilerplate that does not front-load the one fact that matters: that this call deletes a record.

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?

A destructive, single-parameter tool with no output schema and no annotation-adjacent detail in the description. Nothing tells an agent what is destroyed, whether the deletion is reversible, or what a successful response looks like — the definition is inadequate for the risk profile of this 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?

The single required parameter `id` has 0% schema description coverage, and the description does not state what the identifier refers to (data recipient UUID vs. slug) or what happens if it is unknown. With low schema coverage the description needed to compensate and 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 names the resource (data recipients) but describes the action as "viewed or edited," while the tool's actual function per its name is deletion. This is a generic DRF viewset docstring that fails to state the specific operation and would mislead an agent about what the call does.

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 use this tool, no warning that it permanently removes a data recipient record, and no reference to the sibling create/update/retrieve/partial_update endpoints on the same resource that an agent should prefer for non-destructive operations.

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