Api privacy processings list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the opaque phrase "inject optimized data into the serializer context," which conveys nothing about pagination, filtering behavior, permissions, or response shape that an agent could act on.

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?

The single sentence is short but wasted: it is front-loaded with framework internals rather than the resource and operation. Conciseness 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?

A 12-parameter, zero-required list tool with no output schema, no parameter documentation, and no behavioral notes is left almost entirely unexplained. The one sentence provided does not give an agent enough to invoke it reliably.

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% across 12 parameters, and the description compensates for none of it. It does not explain what id, folder, nature, status, perimeters, filtering_labels, assigned_to, search, ordering, limit, offset, or max_pages do, despite this being the primary barrier to calling the tool correctly.

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?

"Override the list method to inject optimized data into the serializer context" describes an internal Django implementation detail, not a user-facing capability. It never states that it lists privacy processing records or what those records represent, leaving the agent to infer the purpose from the tool name 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?

No guidance on when to call this instead of siblings such as ciso_assistant_api_privacy_processings_retrieve, _agg_metrics_retrieve, _export_csv_retrieve, or _object_retrieve. There are no preconditions, exclusions, or alternative-routing instructions of any kind.

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