List Collections (Paged)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and no destructive behavior, so the safety profile is covered. The description adds only that pagination is supported, which is a minor behavioral detail, but does not disclose return format, default sorting, or scoping. There is no contradiction with the 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, front-loaded, efficient sentence with no wasted words. It states the core action and key feature (pagination) without redundancy.

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 too minimal for a tool with no output schema and many sibling listing tools. It does not explain what the response contains, whether it returns all collections or only those for the current user, or how the pagination parameters interact. An agent would need to infer critical context from the name and schema, which is insufficient given the tool's ambiguous placement among transkribus_coll_list, transkribus_coll_list_by_name, and transkribus_coll_list_for_user.

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%, and every parameter has a clear description in the input schema. The tool description adds no parameter-level meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 uses a specific verb ('List') and resource ('collections'), and 'with pagination support' distinguishes it from the unpaged sibling transkribus_coll_list. However, it does not clarify the exact scope of collections (e.g., all accessible vs. current user's) or differentiate it from other collection listing siblings like transkribus_coll_list_by_name and transkribus_coll_list_for_user.

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 description gives no explicit guidance on when to use this tool versus alternatives. It only implies that pagination is the distinguishing use case, but never names when-not-to-use it, does not mention unpaged alternatives, and lacks any exclusion criteria or context about the intended listing scenario.

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