Pay Multiple Invoices

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

No annotations are provided, so the description carries the full disclosure burden. It mentions parallel execution, but for a payment tool it omits critical behavior: whether payments are atomic or partially succeed on failure, whether Lightning payments are irreversible, authorization requirements, and any retry semantics. This leaves the agent guessing about the highest-risk aspects.

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 short sentences with the core action front-loaded; the second sentence earns its place by hinting at the use case, though it is somewhat generic.

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 batch payment tool with no annotations and no output schema, the description should cover partial-failure handling, irreversibility, and what the result reports. None of these are addressed, so an agent cannot reason about how to handle failures across the batch.

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 100%, so both 'invoices' and 'concurrency' (with max/min and default) are already documented in the schema. The description adds no format, ordering, or constraint detail beyond that, so the baseline 3 applies.

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+resource (pay Lightning invoices) with the scoping qualifier 'multiple...in parallel', which naturally distinguishes it from the single-invoice sibling pay_invoice. It does not explicitly name an alternative, but the plural scope is 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?

'Useful for distributing payments to multiple recipients' implies a usage context but stops short of telling the agent when to prefer this over repeated pay_invoice calls or when not to use it. No explicit alternative or exclusion is given.

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