transkribus_admin_get_job_usersGet the users authorized to execute a specific job implementation by providing its job implementation ID.
List users authorized to run a specific job implementation.
| Name | Required | Description | Default |
|---|---|---|---|
| jobImpl | Yes | Job implementation identifier |
Changes observed during successful MCP inspections.
v3.0.0Input schema / properties / jobImpl / patternAdded value: +"^[^/\\s]+$"v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive. Description adds context that it lists authorized users for a specific job implementation, reinforcing safe behavior without contradiction.
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 wasted words. Could be slightly more detailed but adequate for the tool's simplicity.
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?
Tool has one parameter, no output schema. Description sufficiently covers purpose and required input. Complete enough for its complexity.
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 has 100% coverage with description for jobImpl. Description adds no extra meaning beyond 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?
Description clearly states verb 'List', resource 'users authorized', and context 'for a specific job implementation'. It distinguishes from siblings like transkribus_admin_authorize_users_for_job.
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?
Description implies usage (when needing authorized users for a job implementation) but does not explicitly state when to use or avoid, nor mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.