Assign Documents to Label

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

Annotations indicate openWorldHint=true and idempotentHint=false, but the description adds no behavioral context. It does not explain whether assignments are additive or overwriting, or if the tool has side effects. The description fails to clarify behavior beyond the minimal verb.

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?

The description is a single, concise sentence that front-loads the key action and object. It contains no unnecessary words and is appropriately short for a tool with a clear name.

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?

Despite the tool's simplicity, the description is too minimal. It lacks information about whether the operation is additive or full replacement, and does not mention potential constraints like the label must exist. Given no output schema, more context is needed for a complete understanding.

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 both parameters. The description adds no extra meaning or context to the parameters, achieving only the baseline score.

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 'Assign documents to a label' clearly states the action (assign) and the objects (documents to a label). It distinguishes from sibling tools like transkribus_label_assign_pages (assign pages) and transkribus_label_replace_document_assignments (replace assignments), making the purpose unambiguous.

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 is provided on when to use this tool versus alternatives. It does not mention that this tool adds documents to a label (as opposed to replacing assignments), nor does it reference any prerequisites such as the label existing.

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