Get Recent in Collection

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, indicating a safe read operation. The description adds no behavioral context beyond this, such as what 'recently accessed' means, pagination behavior, or response format. With annotations covering safety, a baseline 3 is appropriate.

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 sentence with no wasted words. It is front-loaded with the action. However, it could include more detail without becoming verbose, so it is not a 5.

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?

Given the tool has 5 parameters and no output schema, the description is too minimal. It does not explain what 'recently accessed' means, how sorting works, or the purpose of index/nValues. The annotations provide safety context, but the description lacks sufficient detail for an agent to use the tool effectively.

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 coverage is 100%, so all 5 parameters have descriptions in the input schema. The description does not add any additional meaning or usage context beyond what the schema already provides. Baseline 3 is correct.

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 'Get recently accessed items in a collection' clearly states the verb (Get) and resource (recently accessed items in a collection). It distinguishes from siblings like transkribus_coll_get_recent_collections and transkribus_coll_get_recent_documents by explicitly mentioning 'in a collection'.

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. No when/when-not conditions, prerequisites, or exclusions are mentioned. Sibling tools like transkribus_coll_list or transkribus_coll_find_documents have overlapping purposes but no differentiation is offered.

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