transkribus_page_delete_transcriptDelete a specific transcript version from a document page, removing unwanted transcript data to keep your document clean.
Delete a specific transcript version from a page.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| key | Yes | Transcript key to delete | |
| 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?
Annotations already indicate destructiveHint=true and idempotentHint=true, but the description adds no further behavioral context (e.g., effects of deleting a nonexistent key, side effects of openWorldHint=true). Minimal value beyond annotations.
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, clear sentence with no filler words. Front-loads the action and resource effectively.
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?
Despite having no output schema and destructive nature, the description lacks information on return values, error handling, or what happens when the transcript key is invalid. OpenWorldHint=true suggests possible side effects not explained.
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?
All four parameters have descriptions in the input schema (100% coverage), so the schema already defines their meaning. The description does not add any extra semantic detail.
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 verb (Delete) and the resource (transcript version from a page), distinguishing it from sibling tools like transkribus_page_delete (which deletes the page) and transkribus_page_get_transcript.
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, no prerequisites mentioned, and no exclusion criteria provided. The agent must infer usage from context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.