Check Document Affiliation

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe, non-destructive operation. The description adds no extra behavioral context, such as whether it returns a boolean, lists affiliations, or throws errors for missing documents. Given annotations cover safety, a score of 3 is appropriate.

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, concise sentence without unnecessary words. It is front-loaded with the verb and resource. However, it lacks structure (e.g., no separation of purpose and outcome) and could be more informative without losing conciseness.

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 simple input schema and good annotations, the description still fails to clarify what 'affiliation' means in the Transkribus context (e.g., document affiliation with a collection or organization). There is no output schema, but the description could hint at the return type. The missing context makes it incomplete for an agent to fully understand the tool's utility.

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 both collId and Document ID. The description does not add meaning beyond 'affiliation,' which is not explained in relation to the parameters. Baseline 3 applies as the schema already documents parameters.

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 'Check if a document has an affiliation' with a clear verb and resource, but 'affiliation' is undefined, leaving the purpose vague. It does not differentiate from sibling tools like transkribus_doc_get_metadata or transkribus_doc_get_stats, which might also provide related information.

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. For instance, it does not clarify whether this tool is preferred over checking metadata for affiliation status, nor does it mention prerequisites or context for using the check.

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