Run HTR (CITlab)

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description does not add meaningful behavioral context beyond that. It does not reveal whether the operation is asynchronous, what side effects occur (e.g., job creation, document modification), or if any state changes persist. No contradiction with annotations.

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, clear sentence with no wasted words. It communicates the essential function efficiently and is front-loaded with the core action.

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 (12 parameters, no output schema, basic annotations), the description is insufficient. It does not explain what HTR recognition produces, how results are accessed, or the nature of the operation (e.g., asynchronous job). The openWorldHint suggests external impact, but no details are provided. The presence of many similar siblings demands more context.

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 descriptions for all 12 parameters, so the baseline is 3. The description does not add extra meaning or clarify relationships between parameters (e.g., modelId must be a CITlab model, format for pages). It provides no value beyond the schema, thus scoring the baseline.

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 action (Run), the specific HTR system (CITlab), the type of operation (recognition), the target (a document), and the prerequisite (a specific model). This distinguishes it from other recognition tools like transkribus_pylaia_recognize or transkribus_recog_run_ocr.

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., other recognition tools, or when not to use it). There is no mention of prerequisites, context, or exclusions, leaving the agent without sufficient direction to choose correctly among siblings.

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