Api privacy data subjects destroy

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description frames the endpoint as viewing/editing — the opposite safety profile. It also says nothing about what deletion removes, cascading effects, or irreversibility. This is a direct contradiction of structured data.

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?

One short sentence, so there is no bloat, but it is not front-loaded with anything useful — the only content it contains is inaccurate. Brevity here reflects under-specification rather than economy.

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 mutation with no output schema and no annotations-derived context in the text. The description should say what gets deleted and what happens to linked records; instead it describes a read/edit 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% for the single required `id` parameter, so the description must carry the burden, yet it never mentions the identifier or its format. The agent has to infer that `id` is the data subject's primary key.

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 data subjects to be viewed or edited," which misstates the resource operation entirely — the tool name and the `_destroy` suffix indicate deletion. The resource (data subjects) is identified, but the verb is wrong, so an agent cannot trust the stated purpose.

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 indication of when to use this tool, when not to, or which sibling (e.g. ciso_assistant_api_privacy_data_subjects_update / _retrieve) is the right alternative. Given the dozens of sibling data-subject tools, the absence of routing guidance is a real cost.

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