Replace Page Label Assignments

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

Annotations already indicate idempotentHint=true, readOnlyHint=false, and destructiveHint=false. The description adds that it operates on a 'specific page' and 'replaces' assignments, which is consistent but does not elaborate on side effects (e.g., whether previous assignments are fully overwritten or merged). Given annotations, the description provides minimal additional 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 that directly conveys the core action. It is front-loaded and concise, though it could include a brief note on usage or expected behavior without adding much length.

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?

With three parameters and no output schema, the description fails to explain the semantics of 'replace' (e.g., whether labelIds overrides existing assignments or appends), the relationship between labelId and labelIds, or behavior when labelIds is omitted. This leaves the agent with insufficient information for correct invocation.

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 each parameter (labelId, id, labelIds) is already described in the schema. The description adds no further meaning beyond what's in the schema, earning the baseline score 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 'Replace label assignments for a specific page,' which clearly indicates the verb (replace), resource (label assignments), and scope (page). This differentiates it from sibling tools like transkribus_label_assign_pages (which assigns rather than replaces) and transkribus_label_replace_document_assignments (which operates on documents). However, it could be more explicit about the overwriting behavior.

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_assign_pages, transkribus_label_remove_pages, or transkribus_label_replace_document_assignments. The agent would need to infer usage from the name alone.

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