list-outgoing-payments

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

The description indicates a read-only operation ('List') with no destructive side effects. However, no annotations are present, and the description does not elaborate on behaviors like pagination default behavior or what is retrieved by default.

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 short sentence, very concise. It is front-loaded but could be slightly more informative about the tool's capabilities (e.g., pagination or filtering).

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 tool has 5 parameters including pagination (limit, offset), time range filtering (from, to), and a flag (all), but the description does not mention any of these features. Given no output schema or annotations, the description is too minimal for the tool's complexity.

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?

All 5 parameters have descriptions in the input schema, so the tool description adds no additional parameter details. Baseline score 3 is appropriate given 100% schema description coverage.

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 it lists outgoing payments, but does not explicitly differentiate from sibling tools like 'get-outgoing-payment' (singular) or 'list-incoming-payments'. The verb 'List' and resource 'outgoing payments' are clear.

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 guidance is provided on when to use this tool over alternatives such as 'get-outgoing-payment' for a single payment or 'pay-invoice' for creating payments. No prerequisites or context are mentioned.

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