Api privacy processings update

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

Annotations declare readOnlyHint=false, so this is a mutating call, yet the description claims it is an export mixin — a read-style behavior. That is a direct contradiction of the annotation profile, and the description adds nothing about what is modified, required permissions, or what happens to unspecified fields.

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 that is front-loaded, so it is not verbose. But brevity here is pure under-specification of a mutation tool with two undocumented parameters, and the content that is present is irrelevant.

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 write endpoint with an opaque `body`, no output schema, and zero schema descriptions, the definition supplies none of the context an agent needs to construct a correct call. The description is not just incomplete, it describes a different capability.

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% for both parameters, so the description carries the full burden and provides nothing: no explanation of the required `id`, and no information about the untyped `body` payload (which fields of a privacy processing it accepts). The generic object `body` is especially unhelpful without guidance.

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 describes an export mixin for CSV/XLSX files, which is not what this tool does. The tool name, title, and schema (an `id` plus an update `body`) indicate an update operation on a privacy processing record, but the description never mentions updating or privacy processings. This is actively misleading rather than merely vague.

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 when-to-use guidance is given, and what little is stated ('exports') points the agent at the wrong operation entirely. An agent following this text would look for export siblings such as ciso_assistant_api_privacy_processings_export_csv_retrieve or export_xlsx_retrieve instead of calling this update endpoint.

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