Assign Documents to Label

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, covering the safety profile. The description adds nothing on top of that: it does not explain what happens to existing assignments, whether re-assigning an already-labeled document is an error, or that no output is returned. For a mutation with idempotentHint=false, the duplicate-call behavior is exactly the kind of context that should be disclosed.

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 eight-word sentence with zero padding and the action front-loaded, so there is no wasted verbiage. But the brevity reflects under-specification rather than disciplined conciseness, so it does not earn top marks.

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 operation in a crowded label-tool family, the description omits effect semantics (append vs replace), failure/duplicate behavior implied by idempotentHint=false, and sibling routing. Full schema coverage and safety annotations help, but they do not fill the gaps around mutation behavior and tool selection.

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% (labelId and documentIds are both documented in the schema), so the schema carries the parameter semantics. The description only restates the two concepts at a high level and adds no format, bounding, or batching details, which matches the baseline of 3 when the schema does the heavy lifting.

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 sentence states a specific verb (assign) and two resources (documents, label), so the basic action is legible. However, it is a near-verbatim restatement of the title 'Assign Documents to Label' and gives no differentiation from close siblings such as transkribus_label_assign_pages, transkribus_label_replace_document_assignments, or transkribus_label_remove_documents. It sits between 'clear' and 'tautology'.

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, no prerequisites, and no mention of the alternatives. An agent cannot tell from this text whether assigning appends to existing label membership (vs replace_document_assignments) or how it relates to label_remove_documents. No routing information is provided despite many sibling label tools.

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