tochka_acquiring_payments

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

Annotations already provide readOnlyHint=true, indicating a safe read operation. The description adds pagination and filtering details, which are useful but do not contradict annotations. No additional behavioral traits are disclosed beyond what the annotations imply.

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 concise and uses a clear 'Args:' format. It is front-loaded with the purpose and efficiently lists parameters. Minor improvement could be more natural language, but it is well-structured and not verbose.

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?

Given the complexity of 5 optional parameters and the presence of an output schema (so return values are not needed), the description covers all parameter meanings, defaults, formats, and allowed values. It is fully adequate for agent use.

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 0%, but the description provides detailed explanations for all parameters, including default values, date format (YYYY-MM-DD), and allowed status values. This compensates well for the lack of schema descriptions.

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 'Get list of acquiring payment operations,' which is a specific verb and resource. It distinguishes from siblings like 'tochka_acquiring_payment' (single payment) and 'tochka_acquiring_payment_create' (create operation).

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?

The description lists parameters but does not explicitly guide on when to use this tool versus alternatives, nor does it mention when not to use it. However, the context of retrieving a list is clear.

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