transkribus_doc_remove_from_collectionRemove a document from a Transkribus collection while preserving the document itself. Specify collection and document IDs to detach it without deletion.
Remove a document from a collection without deleting it.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| 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 provide destructiveHint=true and idempotentHint=true. The description adds context that the operation removes without deleting, clarifying the scope of destructiveness. This is helpful beyond what annotations convey.
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, no filler. The description is maximally concise while conveying the essential 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?
For a simple operation, the description adequately states the core action. However, it omits any mention of return values, permissions, or side effects (e.g., document remains in other collections). Given no output schema, some minimal guidance would be beneficial.
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?
Input schema has 100% coverage for both parameters (collId and id). The description does not add extra meaning beyond the schema. Baseline of 3 is appropriate.
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: 'Remove a document from a collection without deleting it.' It specifies the verb 'Remove' and the resources 'document' and 'collection,' and distinguishes from deletion. It differentiates from siblings like transkribus_doc_delete by explicitly stating the document is not deleted.
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 over alternatives like transkribus_coll_remove_doc or transkribus_doc_delete. No mention of prerequisites, when to choose this over other removal operations, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.