paymentSessions.capture

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

No annotations provided, yet the description discloses no behavioral details: it doesn't explain that this moves funds (financial impact), whether it's idempotent, what happens if amount is omitted (full capture?), or error conditions. The phrase 'manually captured' provides no meaningful behavioral context.

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?

While brief at six words, it is inappropriately terse given the complexity (financial operation) and complete lack of schema documentation. The 'manually captured' phrasing wastes space on confusing redundancy rather than adding value.

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?

Completely inadequate for a payment operation tool. No output schema, 0% input schema coverage, no annotations, and the description fails to compensate for any of these gaps. Critical context missing includes currency handling, partial vs full capture logic, and success/failure outcomes.

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 has 0% description coverage, yet the description mentions neither the 'id' parameter (what ID format? is it the session ID?) nor the 'amount' parameter (currency units? optional for full capture?). With zero schema documentation and no description compensation, parameter semantics are completely undocumented.

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 states the verb ('Capture') and resource ('payment session'), but contains confusing phrasing ('manually captured') that suggests the session is already captured. This creates ambiguity about whether this performs a capture or operates on an already-captured session. It minimally distinguishes from siblings like 'refund' or 'void' by using the specific term 'capture'.

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 guidance provided on when to use this tool versus alternatives like 'paymentSessions.refund', 'paymentSessions.void', or 'paymentSessions.continuePayment'. No mention of prerequisites (e.g., session state requirements) or whether this is for partial captures (implied by optional 'amount' param) versus full captures.

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