Api privacy data contractors partial update

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the safety profile is covered there. The description adds nothing operational: it never says this is a PATCH that merges only supplied fields, what happens to omitted fields, or that the record must be addressed by id. Its 'viewed' wording also implies a read capability this endpoint does not have.

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?

One short sentence, front-loaded, with no padding – structurally fine. But its brevity comes from being generic boilerplate rather than from packing in useful signal, so it earns little.

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 mutation endpoint with no output schema, 0% param documentation, and a required id plus free-form body object needs the description to carry the burden of PATCH semantics and payload expectations. It supplies none of that, so an agent cannot invoke it confidently.

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 description gives no parameter information whatsoever. The 'id' parameter and the opaque 'body' object (anyOf arbitrary JSON, additionalProperties true) are completely unexplained, leaving the agent to guess what payload shape the partial update accepts.

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 is DRF boilerplate: 'API endpoint that allows data contractors to be viewed or edited.' It names the resource but never states the actual operation (partial update of one data contractor by id), and it cannot be distinguished from the ~9 sibling contractor tools (list, retrieve, create, update, destroy, object_retrieve, partial_update).

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 when-to-use guidance and no mention of alternatives. Worse, 'viewed or edited' actively points the agent toward reading, which is the job of ciso_assistant_api_privacy_data_contractors_retrieve, not this PATCH-style tool.

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