transkribus_doc_get_statsFetch detailed statistics for a document by supplying collection and document IDs.
Get detailed statistics for a document.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| 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 provide readOnlyHint=true, destructiveHint=false, etc. The description adds only 'Get detailed statistics' without elaborating on what statistics are included or any behavioral traits (e.g., auth needs, rate limits).
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, front-loaded with the key action. Efficient, but could include more detail without overwhelming. No wasted words.
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 no output schema and many sibling tools, the description lacks completeness—it doesn't explain what 'detailed statistics' means or what the return value looks like. Annotations partially compensate but not enough.
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 both parameters (collId, id). The description does not add any extra meaning or context beyond the schema, meeting baseline expectations.
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 states the tool gets 'detailed statistics for a document,' which is a clear verb+resource. However, it does not distinguish this from sibling tools like transkribus_doc_get_stat or transkribus_doc_get_metadata, which may serve similar purposes.
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 vs. alternatives (e.g., transkribus_doc_get_stat, transkribus_doc_get_fulldoc). Does not provide context for selection or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.