Get bank payment

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

Annotations already mark the operation readOnly and idempotent, so the safety profile is covered. The description adds meaningful context: it only fetches payments created by this integration and returns a single object, which is not something the annotations express. It does not address not-found behavior, but that is a minor gap given the simple read operation.

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 with no redundant words. Every phrase ('Fetches', 'one', 'bank payment', 'created by this integration') contributes meaning.

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 simple get-by-ID operation with strong annotations and one required parameter, the description is sufficiently complete: it states what is fetched and the integration scope. It could mention how to find the ID (e.g., via list_bank_payments) and response error behavior, but these are not critical given the tool's simplicity.

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?

The schema coverage is 100% with a description for bankPaymentId ('Path parameter bankPaymentId'), so the baseline is 3. The description adds no further parameter semantics, such as how the ID is obtained or formatted, but none is needed beyond the schema for this simple path parameter.

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 uses a specific verb ('Fetches') with a precise resource ('one bank payment') and adds a scoping constraint ('created by this integration'). This distinguishes it from sibling list/get tools, particularly bokio_list_bank_payments, without requiring schema inspection.

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 or alternative guidance is provided. The singular 'one bank payment' and required bankPaymentId imply use when a specific ID is available, and a sibling list tool exists for discovery, but the description leaves this to inference.

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