Create SBP payment

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

Adds critical behavioral warnings: 'MOVES REAL MONEY — irreversible'—going beyond the destructiveHint annotation by emphasizing the financial impact and irreversibility. Also discloses the return of a confirmation URL/deep-link. No contradiction with annotations.

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 efficient sentences: one states the purpose, the other gives a key behavioral detail and a strong warning. No redundancy or unnecessary information.

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 an output schema present, return details are covered. The description addresses core behavior (confirmation URL, irreversible money movement) but does not discuss conditional parameters like return_url required for redirect, though the schema captures that. Overall adequate.

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%, with each parameter already having a clear description. The tool description itself does not add further parameter-level meaning, 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?

The description clearly states the action ('Create a payment via SBP'), the specific resource (SBP/Russian fast payment system), and distinguishes it from sibling tools like create_payment, create_recurring_payment, and create_split_payment by focusing on SBP.

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?

Provides clear context: this is for SBP payments and returns a confirmation URL/deep-link. However, it does not explicitly compare with alternatives (e.g., create_payment) or state when not to use this tool, so it gets a 4 rather than 5.

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