Replace Document Label Assignments

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds minimal behavioral context; 'replace' implies overwriting existing assignments, but it does not clarify whether all prior assignments are removed or how the combination of labelId and labelIds works. No details on side effects or authentication needs.

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?

Single sentence, no filler. However, it is perhaps too brief to convey necessary detail.

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?

No output schema exists. The description does not explain the behavior of replacement (e.g., whether it removes existing labels before assigning new ones), the effect on the document, or error conditions. Essential context is missing for a mutation tool.

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 100%, but schema descriptions are minimal ('Label ID', 'Resource ID', 'Array of label IDs to assign'). The description adds no extra meaning and fails to explain the ambiguous relationship between labelId (required) and labelIds. This does not compensate for the schema's lack of clarity.

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 'Replace label assignments for a specific document' uses a specific verb ('Replace') and identifies the resource ('label assignments' for a document). It clearly distinguishes from sibling tools like transkribus_label_assign_documents (assign) and transkribus_label_remove_documents (remove).

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 guidance on when to use this tool versus alternatives (e.g., assign or remove labels). No prerequisites or context are provided, leaving the agent to infer usage.

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