Api privacy data contractors update

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing on top – it doesn't say whether the body is a full replacement (PUT semantics), whether partial bodies are accepted, or what permissions are required, which is exactly the gap annotations leave open.

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?

A single short sentence is appropriately sized, but the words chosen carry almost no information beyond the tool name. Being brief is not a virtue when the content is this thin.

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 whose body payload is completely opaque and which has no output schema, the description should explain the expected payload semantics and update behavior. It leaves an agent unable to construct a valid call.

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 provides no parameter guidance at all. The 'id' path parameter is self-evident, but 'body' is a free-form object with additionalProperties=true and no documented shape – the agent has no idea what fields to send or whether omission means deletion.

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 restates the name as 'API endpoint that allows data contractors to be viewed or edited' – it names the resource but in tautological, generic terms. It doesn't distinguish this update from its near-identical siblings (privacy_data_contractors_partial_update, _retrieve, _list, _create), which an agent must choose between.

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 indication of when to use this tool versus partial_update, retrieve, or list. Worse, 'viewed or edited' actively muddies the picture for an endpoint whose name and annotations say 'update', giving the agent no basis for selecting it.

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