List Document Collections

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

Annotations already communicate that this is a safe, idempotent, read-only operation, which cover the behavioral safety profile. The description adds the 'all collections' scope and the document-collection relationship, but does not explain the behavior around the required collId parameter or what output format to expect, so only a minor 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, clear sentence with zero wasted words. It front-loads the primary verb and resource, making it easy for an agent to quickly understand the core function.

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?

The tool requires a collId parameter that is not explained in the description, and the presence of pagination parameters suggests possible paging behavior that is not mentioned. The existence of a paged sibling adds additional ambiguity about how this non-paged version behaves. For an agent to call this correctly, these gaps are significant.

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%, so each parameter has a description, meeting the baseline. The tool description adds no extra meaning about parameters; the relationship between collId and id remains unexplained, and the pagination/sorting parameters are not referenced in the narrative at all.

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 (list) and the resource (collections a document belongs to), which is a specific and useful purpose. However, it does not differentiate this tool from the sibling transkribus_doc_list_collections_paged, leaving ambiguity about which variant to choose.

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?

There is no guidance on when to use this tool versus the paged sibling or other collection-listing tools. The description only states what it does, not the context or conditions under which it is the appropriate choice.

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