Assign Pages to Label

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds nothing on top of that — it does not say whether assignment is additive or overwrites existing assignments, whether it requires edit permissions on the collection, or what limits exist. With annotations present the bar is lower, but this contributes no behavioral context at all.

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?

It is a single short sentence with zero filler, which is structurally clean and front-loaded. However, it is under-specified rather than genuinely concise — it conveys no more information than the tool name already does.

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 with no output schema and no annotation-level detail on assignment semantics, the description leaves key questions unanswered: whether existing page assignments are replaced or appended, and whether pageIds are collection-scoped. An agent calling this correctly needs more than the name restated.

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% with only two parameters (labelId, pageIds), so the schema already documents both fully. The description adds no syntax, format, or constraint detail beyond what the schema provides, which lands at the baseline of 3.

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 states a specific verb and resource ('assign pages to a label'), but it is essentially a verbatim restatement of the title 'Assign Pages to Label.' It gives no differentiation from close siblings such as transkribus_label_replace_page_assignments, transkribus_label_remove_pages, or transkribus_label_assign_documents, so an agent gets the general action but no disambiguation.

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 alternatives. Given siblings like label_replace_page_assignments (which likely overwrites) and label_remove_pages, the description gives no signal about how this additive assignment differs from those operations.

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