Api privacy data subjects object retrieve

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

Annotations declare readOnlyHint=true and destructiveHint=false, yet the description says the endpoint allows data subjects to be 'viewed or edited', implying a write capability this endpoint does not have. This directly contradicts the read-only annotation, and no other behavioral context (permissions, missing-id handling, response shape) is provided.

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 with no padding, but its brevity reflects boilerplate rather than front-loaded precision; nothing informative leads the definition.

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 retrieve-by-id endpoint with no output schema and a 0%-documented parameter, the description should explain the identifier and the returned resource. It says nothing about either, and its 'edited' claim actively misleads about the 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 coverage is 0% and the single required parameter 'id' is untyped in both schema and description. The description says nothing about what the id refers to (object UUID vs ref_id) or how to obtain it, so it fails to compensate for the coverage gap.

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 restates the name in generic DRF boilerplate ('API endpoint that allows data subjects to be viewed or edited') rather than stating that it retrieves a single data subject object by id. It does not distinguish this from siblings such as privacy_data_subjects_retrieve, privacy_data_subjects_list, or privacy_data_subjects_object_retrieve, and the phrase 'or edited' muddies whether this is a read operation at all.

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 endpoint versus the many sibling data-subject endpoints (list, retrieve, cascade_info, category, batch_action). The implied usage is 'fetch a data subject', but nothing states prerequisites or alternatives.

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