Replace Page Label Assignments

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it does not explain what 'replace' destroys (existing assignments), whether it needs write permission, or how it behaves with an empty labelIds array.

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 with the action and target front-loaded and zero filler. It is efficient, though its brevity is also the source of the other gaps.

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 mutation tool sitting in a dense sibling cluster, the description is too thin. It omits the replace-vs-assign semantics, the labelId/labelIds relationship, and any permission context; annotations cover safety but not behavior, and there is no output schema to fall back on.

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 100%, so the schema already documents id, labelId, and labelIds, making the baseline a 3. However, the description does not resolve the real ambiguity here: why both a required single labelId and an optional labelIds array exist, or how they interact during a replace.

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 names a verb (replace) and resource (label assignments) and scopes it to 'a specific page', but it is essentially a paraphrase of the title 'Replace Page Label Assignments'. It never distinguishes itself from close siblings like transkribus_label_assign_pages or transkribus_label_replace_document_assignments, leaving the agent to infer the difference from the tool 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?

There is no when-to-use guidance and no alternatives named, despite an obvious sibling cluster (label_assign_pages, label_remove_pages, label_replace_document_assignments). The agent is not told when replace is preferred over plain assign.

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