Get Recent Collections

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destuctiveHint=false, covering the safety profile. The description adds the 'recently accessed' behavioral scoping, but it does not disclose return format, pagination, or any auth expectations, so additional context is limited.

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 sentence with no wasted words. Every word contributes to the tool's purpose, and there is no unnecessary verbosity.

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?

Despite 4 parameters and no output schema, the description only offers a minimal phrase. It does not explain how the parameters interact, what the returned list looks like, or how this tool relates to the many nearby collection-list siblings, leaving an agent under-informed for correct invokation.

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 the schema already documents the index, nValues, sortColumn, and sortDirection parameters. The description adds no param-level meaning beyond that, which keeps it at the baseline for complete schema coverage.

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 clear verb+resource ('Get recently accessed collections'), so an agent knows what the tool does. However, it does not differentiate it from the sibling tool transkribus_coll_get_recent, which appears to overlap in function, so it stops short of full sibling distinction.

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 provides no guidance on when to use this tool versus alternatives such as transkribus_coll_get_recent, transkribus_coll_list_paged, or transkribus_coll_list. There is no mention of exclusions, prerequisites, or a preferred context.

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