list_documents

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

Annotations already declare the tool as read-only and non-destructive, so the description does not need to restate that. It adds useful behavioral context about time-window filtering and source filtering, but does not describe output shape, pagination, or document availability behavior.

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 compact and front-loaded with the core behavior, followed by parameter guidance. No filler or redundant restatement of annotations or schema exists.

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 adequate for calling the tool with correct parameters, and annotations cover safety. However, there is no output schema and the description does not indicate what the returned document list contains, whether it includes metadata or download links, or how it relates to download_documents.

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%, but the description compensates fully: since_days is explained as the lookback window, source is given allowed values (all | postbox | transactions), and title_contains is described with a concrete example. This is strong beyond the bare schema.

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 clearly states that the tool lists documents within a time window and names the document categories (account statements, trade confirmations, etc.). It is distinct from siblings like download_documents by verb and resource, though it does not explicitly differentiate itself from any sibling.

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?

No when-to-use or when-not-to-use guidance is provided. The description explains parameters but never tells the agent when to choose list_documents over alternatives such as download_documents or get_transactions.

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