Export Document

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description carries the burden of disclosing behavioral traits. Beyond 'Export', it does not explain side effects (e.g., does it create a job, modify the document, or return a direct download?). No additional context is provided.

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 sentence, which is concise but lacks any structural elements that could improve usefulness (e.g., bullet points for key parameters or usage notes). It is not bloated, but could be more informative in the same space.

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 complexity of 37 parameters and no output schema, the description is too sparse. It does not mention the return type, whether the export triggers an asynchronous job, or how to access the exported file. Annotations and schema partially compensate, but the description falls short.

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% with clear, self-explanatory descriptions for all 37 parameters. The tool description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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 'Export a document in the specified format' clearly indicates the action (export) and the resource (document), and distinguishes it from sibling tools like delete or get operations. However, it lacks specificity about what 'export' entails (e.g., downloading a file vs. creating a new document).

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 is provided on when to use this tool versus alternatives like transkribus_coll_export, transkribus_doc_get_mets, or transkribus_doc_get_fulldoc. The description does not mention prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.