transkribus_user_getRetrieve detailed information about a specific Transkribus user by providing their numeric user ID. Returns user profile details for the given ID.
Get details of a specific user by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Resource ID |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description does not add behavioral context beyond what annotations convey. It is not contradictory, but adds no extra value here.
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?
One sentence, 8 words, front-loaded with the verb 'Get'. Every word is necessary and there is no fluff.
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 get-by-ID tool with strong annotations and a single well-described parameter, the description is sufficient. It covers the purpose and required input. No output schema exists, but that is acceptable given the 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 description coverage is 100% (parameter 'id' has description 'Resource ID'). The tool description says 'by ID' which essentially restates the schema. No additional meaning provided 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 verb 'Get', resource 'details of a specific user', and the means 'by ID'. It effectively distinguishes from sibling tools like transkribus_user_list and transkribus_user_find.
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 like transkribus_user_list (for listing all users) or transkribus_user_find (for searching by criteria). The description implies you need a specific ID but does not explicitly state the context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.