user_pay_get

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

With no annotations, the description carries the full behavioral burden, yet it only restates the HTTP verb and route. It says nothing about authentication requirements, whether user_id implies admin impersonation semantics in responses, pagination defaults, or what the collection contains — all of which an agent needs before calling.

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?

It is short, but a meaningful share of the text is scaffold ('GET /user/pay', 'Тег:', 'Спека:') rather than information. The one substantive sentence is front-loaded, which is the only structural strength.

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?

There is no output schema and no description of the returned payment records, their fields, or pagination envelope, so an agent cannot anticipate the response. Combined with zero annotations, the definition leaves the tool's behavior largely unspecified.

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 limit, offset, and user_id each documented inline, so the schema already does the work and a baseline 3 applies. The description adds no parameter meaning of its own.

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 phrase 'Список платежей пользователя' (list of user payments) does convey a verb+resource, but it is generic and gives no scope, filtering, or ordering information. It does not distinguish itself from the near-namesake sibling admin_user_pay_get, so an agent must open both schemas to tell them apart.

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 statement of when to use this tool versus admin_user_pay_get, user_pay_forecast_get, or user_pay_paysystems_get, nor any prerequisite or context. The 'Тег: Платежи' / 'Спека: user' lines are raw spec metadata, not usable guidance.

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