Api privacy data breaches object retrieve

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

The description claims the endpoint allows records to be 'edited', which directly contradicts the readOnlyHint=true and destructiveHint=false annotations and duplicates the role of the _update/_partial_update siblings. It adds no context about authentication, response shape, or what is returned for a given id.

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 with no bloat, but the content is boilerplate rather than front-loaded signal. Nothing about the sentence could not be inferred from the tool name.

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?

With no output schema and no parameter documentation, the description is the only place return contents and identifier semantics could be explained, and it says nothing. For a one-parameter read endpoint this is still a significant gap given the crowded namespace of near-identical privacy data-breach tools.

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% and the single required 'id' parameter is documented nowhere; the description does not say that it is the breach identifier nor what form it takes. The only saving grace is that a lone path id is largely self-evident from the '_object_retrieve' suffix.

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 generic Django-REST-Framework boilerplate 'allows data breaches to be viewed or edited' names the resource but hedges between read and write, and does not distinguish this object-level retrieve from the sibling ciso_assistant_api_privacy_data_breaches_retrieve or from the _update/_partial_update variants. An agent cannot infer that this is a single-record fetch keyed by id from the description alone.

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 _list, _retrieve, or _update siblings, and no mention of the required id or that this is a read-by-identifier operation. The agent is left to infer usage entirely 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.