List Documents

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

With no annotations, the description carries the behavioral burden. It correctly communicates that this is a non-mutating listing operation, supports folder filtering, and names three sort dimensions. However, it does not disclose pagination or limit behavior, nor does it explicitly state that the tool returns document metadata/summaries rather than full content, though the output schema partially compensates.

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 front-loaded sentence states the action, scope, optional filter, and sort choices with no filler. Every phrase earns its place, and the most important information ('List documents') appears immediately.

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?

For a simple list operation with three optional, defaulted parameters and an output schema, the description covers the main selection and invocation traits. It is slightly incomplete only in not flagging when to prefer mendeley_search_library over this tool and not specifying pagination behavior, but these are minor given the low complexity and existing schema.

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 0%, so the description must add parameter meaning. It adds semantic value by explaining that sort_by corresponds to last modification, creation date, or title, and that folder_id filters by folder; limit is left implicit despite having a default. The human-readable sort labels are not quoted as exact API values, which could lead an agent to pass invalid sort strings.

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 opens with the specific verb 'List' and a concrete resource ('documents from the library'), clearly distinguishing it from sibling operations like mendeley_search_library, mendeley_get_document, and folder-management tools. It also states the optional folder filter and sort options, leaving no ambiguity about the tool's core function.

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 implies a clear use case—obtain a listing of library documents, optionally scoped to a folder—but it never names sibling alternatives such as mendeley_search_library, which should be used for text/content search, or mendeley_get_document for a single document. There is no explicit when-to-use/when-not-to-use guidance, so the agent must infer selection from the verb 'list' alone.

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