Api privacy purposes object retrieve

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

The annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, but the description says the endpoint allows purposes to be 'viewed or edited', implying write capability on a read-only tool. This is boilerplate DRF docstring text rather than a functional claim, but it still points the agent in the wrong direction and adds no real behavior context (no return shape, no 404-on-missing-id behavior).

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, so there is no bloat, but the space it does occupy is spent on a misleading 'viewed or edited' clause rather than on a scoping fact. Brevity here reflects under-specification, not efficiency.

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 one-parameter read tool with no output schema, the description still needs to say what a 'purpose' record is (a GDPR processing-purpose object in the privacy module) and what a successful call returns. Neither is present, and the edit hint actively conflicts with 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 single `id` parameter has 0% schema description coverage, so the description carries the full documentation burden and says nothing about its type, format, or whether it is the numeric PK or the object's ref_id/str identifier. An agent receiving only this description has no guidance on how to form a valid 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 description says the endpoint 'allows purposes to be viewed or edited', which loosely names a verb and resource but is essentially a restatement of the tool path in prose. It does not distinguish this 'object_retrieve' variant from the sibling ciso_assistant_api_privacy_purposes_retrieve or ciso_assistant_api_privacy_purposes_list, so an agent cannot tell which of the near-identical purpose tools to call.

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 statement of when to use this tool, no prerequisites, and no mention of the sibling list/retrieve/update tools as alternatives. Worse, the note that purposes can also be 'edited' invites the agent to use this read-only tool for a write operation instead of ciso_assistant_api_privacy_purposes_update.

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