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

Annotations already flag this as non-read-only, destructive and non-idempotent, so the safety bar is lower. The description does add real context with 'optimistic revision checks', telling the agent that a stale revision will fail the call. However, it never clarifies whether 'update' replaces the whole draft profile or merges fields, which is exactly what makes the operation destructive here.

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 front-loaded sentence with no filler, but its brevity is achieved partly by omitting the operation's semantics rather than by tight editing.

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?

There is no output schema and annotations only cover safety flags, so the description must explain conflict behavior and update semantics; it does neither. An agent knows what to call but not what a revision mismatch returns or whether omitted fields are cleared.

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%, so the description must carry the burden. It only hints at the meaning of 'revision' (optimistic concurrency) and says nothing about draft_id or the required full 'profile' payload, leaving two of three required parameters undocumented anywhere.

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?

States a specific verb and resource ('Update ... draft') plus meaningful scope: the authenticated submitting agent's own unconfirmed draft. It does not explicitly contrast with create_manufacturer_draft, but the name/verb pairing makes the operation distinguishable from a creation tool.

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?

The word 'unconfirmed' implies a precondition (only drafts not yet confirmed can be updated), but there is no explicit when-to-use guidance, no mention of the sibling create_manufacturer_draft, and no statement of what to do when the draft is already confirmed.

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