transkribus_job_createCreate a new processing job to run Transkribus tasks on a chosen document or collection by specifying the job type and optional IDs.
Create a new processing job.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Job type | |
| docId | No | Document ID to process | |
| collId | No | Collection ID to process |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-read-only behavior. The description confirms mutation but adds no new behavioral context (e.g., side effects, required permissions, or response format). With annotations present, the description's contribution is minimal.
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 (5 words) but overly vague. While front-loaded, it sacrifices necessary detail for brevity, making it less useful than a slightly longer but more informative description.
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?
Given the tool has required parameters and no output schema, the description should at least hint at required inputs, return behavior, or linkage to other job tools. It lacks this context, leaving the agent underinformed.
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 description coverage is 100%, so baseline is 3. The description does not add any parameter-specific meaning beyond the schema, such as explaining what 'type' values are expected or how docId/collId relate to job creation.
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 and resource ('Create a new processing job'), but does not distinguish from sibling tools like transkribus_job_update or transkribus_job_kill, missing an opportunity for differentiation.
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 provides no guidance on when to use this tool versus alternatives (e.g., transkribus_job_update for modifying jobs, transkribus_job_list for listing). No context on prerequisites or appropriate scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.