Get Bulk ISAD Metadata

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds no additional behavioral context beyond stating the basic action. It does not contradict 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 short sentence that conveys the core purpose without extraneous words. It is front-loaded. However, it could benefit from slightly more context without becoming verbose.

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 only one parameter and no output schema, the description lacks essential context about what 'bulk ISAD(G) metadata' entails and when to prefer this tool over similar ones like 'transkribus_upload_get_bulk_doc_metadata'. Absence of return value expectations or typical use cases makes it incomplete for an agent unfamiliar with Transkribus.

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?

The input schema has one parameter (collId) with a description in the schema. The description does not add meaning beyond the schema, leaving the agent to infer that the collection ID relates to uploads. Schema coverage is 100%, so baseline 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 includes a clear verb ('Retrieve') and resource ('bulk ISAD(G) metadata'), and specifies the scope ('for uploads'). However, it does not differentiate from the sibling tool 'transkribus_upload_get_bulk_doc_metadata', which suggests a similar purpose for different metadata types.

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. The description does not mention prerequisites, exclusions, or related tools. Annotations indicate it is read-only and idempotent, but this is not leveraged in the description.

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