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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the returned payment fields, including invoice allocation (amount_used) and remaining balance (amount_left), but does not discuss pagination behavior or result ordering beyond what the schema states.

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 front-loaded sentence plus the endpoint, with no wasted text. It efficiently communicates the resource and the notable return fields.

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?

With no output schema, the description usefully names the key payment fields and the allocation/remaining amounts an agent will receive. Combined with the fully described schema and read-only annotations, this is largely complete, though it could mention pagination or default sorting more explicitly.

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 all 14 parameters are thoroughly documented in the schema itself. The description does not add parameter-level meaning or filter syntax, but the baseline for fully documented parameters is 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 identifies the resource clearly: recorded income and expense payments, with key fields such as amount, method, date, counterparty, amount_used, and amount_left. It also gives the endpoint GET /payments, making the listing purpose evident, though it does not explicitly distinguish itself from invbg_get_payment or invbg_list_bank_transactions.

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?

There is no explicit guidance on when to use this tool versus invbg_get_payment or the bank-transaction listing tools. The description implies a generic payment listing but offers no exclusions, prerequisites, or alternative-selection guidance.

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