Api privacy personal data object retrieve

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

The description says the endpoint allows data to be 'viewed or edited', directly contradicting the annotation readOnlyHint=true and destructiveHint=false. No additional behavioral context (permissions, what is returned, scoping) is provided, and the stated capability is factually inconsistent with the declared safety profile.

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 with no wasted words, but that brevity comes from boilerplate rather than precision — it is under-specified rather than concise, and the only substantive claim it makes is 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?

A retrieve tool with no output schema and an undocumented id parameter needs the description to convey what entity is returned and how it differs from list/retrieve variants. It conveys none of this and actively misleads about mutability.

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 no schema description (0% coverage), and the description adds nothing about its format, whether it is the object's UUID/slug, or what it identifies. Minimal compensation for the schema gap beyond the obvious reading of 'id'.

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 sentence is generic Django REST Framework boilerplate: it names the resource ('personal data') but gives a scope-less, dual-purpose verb ('viewed or edited') that doesn't reflect a single-object retrieve. It provides no way to distinguish this from siblings like privacy_personal_data_retrieve, privacy_personal_data_list, or privacy_personal_data_object_retrieve.

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 on when to use this tool versus the numerous sibling personal-data endpoints (list, retrieve, create, update, partial_update, batch_action). The agent must infer selection purely from the tool name.

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