Run Text2Image

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

Annotations indicate it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description confirms it 'runs' an alignment, implying a job is started, but it does not disclose potential side effects, asynchronicity, or that it requires credits. The description adds minimal behavioral context beyond what annotations imply.

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, very concise (10 words), and front-loaded with the key action and resource. However, it could include more detail without becoming verbose. It earns a 4 for efficiency, not penalized for lack of completeness in this dimension.

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 tool's complexity (5 parameters, no output schema, open-world hint, many siblings), the description is severely lacking. It does not explain what 'Text2Image alignment' entails, how the 'body' parameter configures it, what the return value is (likely a job ID), or how credits are consumed. The description is insufficient for an agent to use this tool correctly without additional knowledge.

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%, so the input schema already describes all parameters (e.g., collId, modelId, body, credits, doNotDeleteWorkDir). The description does not enhance understanding of what these parameters mean or how they interact. Baseline 3 is appropriate since the schema does the heavy lifting.

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) and resource (Text2Image alignment) and context (using a specific model in a collection). However, it does not differentiate this tool from sibling tools like transkribus_recog_text2image_citlab or transkribus_recog_text2image_matching, which have similar names and likely 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 is provided on when to use this tool versus its siblings. There is no mention of prerequisites, appropriate contexts, or circumstances where this tool should be avoided. The description merely states what it does without helping the agent decide when to invoke it.

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