Assign Pages to Label

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

The description only says 'assign' without detailing behavioral traits beyond what annotations provide. Annotations indicate openWorldHint=true but provide no specifics on side effects, permissions, or whether assignments are cumulative. The description adds no meaningful behavioral context.

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 sentence with no wasted words. It is as concise as possible, though it sacrifices completeness.

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?

Given the tool modifies page-label assignments, the description lacks important context such as whether assignments are added or replaced, what happens if the label or pages are invalid, and any prerequisites. The annotations and schema do not compensate for this missing information.

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%, so the input schema already describes both parameters (labelId and pageIds). The description adds no additional semantic value beyond the schema descriptions.

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 clearly states the action (assign) and resources (pages, label). It distinguishes from sibling tools like transkribus_label_assign_documents by focusing on pages rather than documents, but does not differentiate from transkribus_label_replace_page_assignments.

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 such as transkribus_label_replace_page_assignments or transkribus_label_remove_pages. The context of usage (e.g., additive vs. replacement) is missing.

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