List Deposits

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

Adds sorting behavior ('newest first') beyond read-only annotations. Consistent with idempotentHint and destructiveHint. Could mention no side effects, but annotations already cover that.

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?

Clear and front-loaded with main purpose. Includes a helpful example. Slight redundancy with Spanish version, but acceptable.

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 output schema exists, description adequately covers pagination, filtering, sorting, and example. No gaps for a list operation.

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 has 100% coverage, but the description adds value by showing example usage and explaining pagination/filtering context. The example integrates parameters effectively, exceeding a baseline 3.

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 'List all deposits' with optional pagination and date filters, and provides a concrete example. It distinguishes from siblings like 'get_deposit' (single) and 'create_deposit' (mutation).

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 explicit when-to-use vs alternatives. While the example and context imply it's for bulk listing, the description does not directly state when to prefer this over 'get_deposit' or other listing tools like 'search_invoices'.

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