List Document Collections (Paged)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the pagination behavior but does not disclose details such as default page size, maximum page size, or behavior when nValues is -1. 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?

A single sentence that conveys the core action, the resource, and the pagination trait without redundancy. It is front-loaded and every word earns its place.

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 description is thin for a 6-parameter tool with no output schema. Most notably, it requires collId even though the tool's stated purpose is listing all collections a document belongs to—it never explains why the collection ID is needed or how it scopes the result. It also says nothing about the response format or how pagination parameters interact.

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 every parameter is already documented in the schema. The description does not add parameter-level meaning beyond 'with pagination', which loosely references index and nValues. Baseline 3 is appropriate because the schema carries the semantic weight.

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 a specific verb and resource—'List all collections a document belongs to'—and appends 'with pagination' to distinguish it from the unpaged sibling transkribus_doc_list_collections. This leaves no ambiguity about what the tool does.

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 phrase 'with pagination' implies this tool is for paginated access, but it provides no explicit when-to-use or when-not-to-use guidance. It does not mention the alternative non-paged tool transkribus_doc_list_collections or any conditions that would select one over the other.

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