transkribus_coll_delete_emptyDelete an empty collection from Transkribus to clean up your workspace. Ensures only collections without documents are removed.
Delete a collection only if it is empty.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 include destructiveHint: true and idempotentHint: true. The description adds the conditional behavior (only if empty), which is not captured by annotations. No contradictions.
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 short sentence that front-loads the key behavior. No wasted words.
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 conditional delete with one parameter and no output schema, the description is adequate. It could mention error handling (e.g., if collection not empty or not found), but the core behavior is clear.
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?
Only one parameter 'collId' with schema description 'Collection ID'. Schema coverage is 100%, so description does not add extra meaning beyond the schema. Baseline 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 name 'Delete Empty Collection' and description 'Delete a collection only if it is empty.' clearly state the action and condition. This distinguishes it from 'transkribus_coll_delete' which presumably deletes any collection.
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?
The description implies when to use (safe deletion of empty collections). It does not explicitly state prerequisites or when not to use, but the sibling tool name suggests an alternative for non-empty collections.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.