List documents

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

Annotations already communicate read-only, idempotent, open-world behavior. The description adds useful behavioral detail: results are newest first and the returned set includes more than the invoice/receipt type filter values. It does not detail pagination behavior, but the schema covers per_page limits and defaults.

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?

Two compact sentences with no filler. The first sentence front-loads the action, scope, and ordering; the second summarizes the filter dimensions. It earns its place without repeating the full schema.

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 read-only list tool with no required parameters, rich schema descriptions, and safe annotations, the description is complete. An agent can select the tool and form valid filter-based requests without missing essential information.

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 descriptions cover most parameters, so the description's filter summary maps cleanly onto existing fields: type, start/end_date, partner_id, payment_status/method, and block_id. This grouping adds mild semantic value, but it does not introduce syntax or meanings beyond what the schema already provides.

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?

States a specific verb and resource: 'Lists documents', and adds scope ('invoices, receipts, proformas, drafts and more') plus ordering ('newest first'). This clearly distinguishes it from single-document siblings like get_document or download_document.

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 establishes a clear listing context and explains available filters, so an agent can infer it is for retrieving a filtered collection. However, it does not explicitly contrast with sibling tools or state when not to use it, stopping just short of full guidance.

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