transkribus_recog_text2image_citlabRun CITlab Text2Image alignment on a collection to synchronize text and image content. Specify collection ID and alignment settings to execute the process.
Run CITlab Text2Image alignment for a collection.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Text2Image configuration parameters | |
| 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 indicate non-read-only, non-destructive, non-idempotent, and open-world behavior, but the description adds no additional context about side effects (e.g., job creation, resource modification). The description does not disclose expected changes or permissions needed.
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 a single concise sentence, but it lacks secondary details that would aid understanding. It is front-loaded but too brief.
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?
With nested objects and no output schema, the description is insufficient. It does not explain the effect on the collection, how results are returned, or how to monitor progress, leaving significant gaps for an agent.
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% with basic descriptions for collId and body, but the description adds no further meaning. The 'body' parameter is a complex object with undefined structure; the description does not clarify required configuration fields, leaving ambiguity.
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 runs a CITlab Text2Image alignment for a collection, using specific verb 'Run' and resource 'CITlab Text2Image alignment'. However, it does not differentiate from sibling tools like transkribus_recog_text2image, which may use a different engine.
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 (e.g., other text-to-image tools or OCR engines). No prerequisites or context for invocation are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.