Api privacy data recipients object retrieve

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

The description says the endpoint allows data recipients to be 'viewed or edited', while annotations declare readOnlyHint=true and destructiveHint=false. This directly contradicts the read-only nature of the tool, so the description misleads an agent about mutation capability.

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 front-loaded sentence with no padding, which is structurally fine. However, the boilerplate wording includes misleading content ('edited') rather than useful scoping information.

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 no documented id semantics, the description should explain what is returned and how the id is interpreted. Instead it provides only generic DRF boilerplate and contradicts the read-only annotation.

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 schema has one required 'id' parameter at 0% description coverage. The description adds no meaning about what the id identifies (e.g., a data recipient ID) or how it is used, so it fails to compensate for the undocumented parameter.

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?

It names the resource ('data recipients') but the verb is ambiguous ('viewed or edited'), and since this is a retrieve endpoint the 'edited' part misstates the operation. It also fails to distinguish itself from sibling recipient endpoints such as privacy_data_recipients_retrieve, _list, and _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 endpoint versus the many sibling recipient endpoints. An agent gets no help choosing between object_retrieve, retrieve, or list, and no prerequisites or exclusions are stated.

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