tochka_acquiring_payment_capture

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

The description only says 'Capture funds', which implies mutation, but does not disclose side effects, idempotency, rate limits, or auth requirements. The annotation 'openWorldHint: true' hints at unknown behavior, but the description adds no additional behavioral context beyond the annotation.

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 extremely concise, consisting of a single sentence and an argument list with no wasted words. However, for a financial capture tool, it may be too terse, missing critical usage context.

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 it has an output schema, the description need not explain return values, but it lacks context about the two-stage flow, prerequisites, and typical usage. This is insufficient for an agent to correctly invoke the tool without additional domain knowledge.

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?

With 0% schema description coverage, the description attempts to define 'operation_id: Payment operation ID', but this adds minimal value over the schema's title 'Operation Id'. It does not specify format, source, or constraints, leaving the agent without adequate guidance.

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 'Capture funds for two-stage acquiring payment', using the specific verb 'capture' and resource 'funds', which distinguishes it from sibling tools like 'tochka_acquiring_payment_create' (create) and 'tochka_acquiring_payment_refund' (refund).

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 implies usage in a two-stage process (capturing after authorization) but does not explicitly state when to use this tool vs. alternatives like 'tochka_acquiring_payment_create' or the prerequisites for the operation_id. The agent is left to infer the context.

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