transkribus_crowdsource_unsubscribeUnsubscribe from a crowdsourcing project for a collection by supplying the collection ID. End your participation and stop receiving related tasks.
Unsubscribe from a crowdsourcing project for a collection.
| 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 already indicate destructiveHint=true and idempotentHint=true. The description does not add further behavioral context such as side effects or permissions beyond the obvious unsubscribe action.
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?
The description is short and to the point, with no unnecessary words. It could be slightly more structured, but it is efficient.
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 one-parameter tool, the description is minimal. It does not explain what happens after unsubscribing or any side effects, but it is arguably sufficient given the tool's simplicity.
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% for the single parameter 'collId', which is described as 'Collection ID'. The description mentions 'for a collection' but adds no new meaning beyond the schema.
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 'Unsubscribe' and the resource 'crowdsourcing project for a collection'. It is specific and distinguishes from the sibling tool 'transkribus_crowdsource_subscribe'.
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 usage when one wants to unsubscribe from a crowdsourcing project, but it does not provide guidance on when not to use it or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.