transkribus_doc_update_transcriptUpdate a transcript for a specific page in a document using collection, document, and page identifiers. Specify optional status or file name to sync changes.
Update a transcript for a specific page in a document.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| page | Yes | Page number | |
| collId | Yes | Collection ID | |
| status | No | Transcript status | |
| fileName | No | File name for transcript sync |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-read-only, non-destructive, and idempotent behavior. The description confirms 'update' but adds no additional context beyond that. It does not explain what happens if the transcript doesn't exist, concurrency effects, or the extent of the update (full replace vs. partial).
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, clear and direct. No redundancy. Front-loaded with the action. Could be slightly more descriptive, but overall concise and to the point.
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: no output schema, no details on return value or error behavior. Does not explain if the update replaces the entire transcript or applies to specific fields. With 5 parameters and complexity of transcript updates, the description is insufficient for full understanding.
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 schema already documents all parameters. The description does not provide any additional meaning or usage tips for parameters like 'status' or 'fileName'. Baseline 3 is appropriate since 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 description clearly states it updates a transcript for a specific page in a document. It distinguishes from sibling tools like transkribus_page_post_transcript (which likely creates a new transcript) and transkribus_page_update_transcript_status (which only updates status). The scope is specific and the verb 'update' is appropriate.
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 versus alternatives like transkribus_page_post_transcript or transkribus_page_update_transcript_status. It does not mention prerequisites (e.g., existing transcript or page) or contextual conditions (e.g., page locking).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.