Replace Document Label Assignments

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

Annotations already disclose readOnlyHint=false, idempotentHint=true, and destructiveHint=false, which is the key safety profile for a 'replace' mutation. The description adds nothing beyond that — it does not say whether prior assignments are discarded, whether the call is transactional, or what authorization is required — but the annotation bar is met, so a middle score is appropriate.

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 clean sentence with the verb and scope front-loaded and no filler. It is efficient, though its brevity shades into under-specification given the tool's ambiguity.

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/replace operation with three parameters, a confusing labelId/labelIds pairing, no output schema, and several near-identical sibling tools, the description leaves too much unsaid: replace-vs-assign semantics, the fate of existing assignments, and how the two label parameters combine.

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 coverage is nominally 100%, but the schema descriptions are generic ('Label ID', 'Array of label IDs to assign') and the crucial ambiguity is left unresolved: both 'labelId' and 'labelIds' exist, with labelId required, yet the description never explains how the singular required ID relates to the array to be assigned. This is exactly the kind of meaning the description should supply and does not.

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 ('Replace') and resource ('label assignments') scoped to 'a specific document', so the operation itself is unambiguous. It does not differentiate from the sibling transkribus_label_assign_documents (which presumably adds rather than replaces) or from transkribus_label_replace_page_assignments, so an agent must infer the distinction from the 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 when-to-use guidance at all. With siblings like label_assign_documents, label_remove_documents, and label_replace_page_assignments present, the agent gets no help deciding which of these four label-mutation tools applies, nor any stated prerequisite (e.g. label must exist, document must be accessible).

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