transkribus_page_replaceReplace a specific page image in a Transkribus document by providing the collection ID, document ID, and page number.
Replace a page image in a document.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| page | Yes | Page number | |
| collId | Yes | Collection ID |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description says 'replace' implying mutation, but annotations show destructiveHint=false and idempotentHint=true; no further behavioral details provided (e.g., what happens to old image, permissions needed).
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?
Single sentence, front-loaded, no redundant information. Every word serves a purpose.
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?
Missing critical context: how the new image is provided (no image parameter in schema), no output specification, and no mention of side effects. Despite simple parameters, the tool is a mutation and should explain what happens to the old image.
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 descriptions cover 100% of parameters; description does not add new meaning beyond what the schema provides. 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?
Description clearly states verb (replace) and resource (page image), distinguishing it from sibling tools like add, delete, move.
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 on when to use this tool vs alternatives like transkribus_page_add or transkribus_page_delete. Lacks prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.