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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so safety is covered structurally. The description usefully adds that it re-checks KYC/payout readiness and does not itself charge money, but omits prerequisites (e.g. KYC failure behavior), failure modes, and what state it mutates in preparation.

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 compact sentences with the action front-loaded and the key caveat ('never charges money by itself') placed as a clear closing constraint. No filler.

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?

An output schema exists, so return values need not be described, and complexity is low with one required parameter. The description covers the essential nature of the step, though it could note preconditions for the handoff to succeed.

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 a single parameter at 100% schema description coverage, the schema already defines order_id and its meaning. The description adds no extra semantics about the parameter, 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?

States a specific verb and resource: it re-checks seller KYC/payout readiness and prepares the Stripe Connect funding handoff. This differentiates it from pure payment siblings like nexus_trade_create_payment_intent, though it doesn't name a specific alternative it must not be confused with.

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 phrase 'prepare the order's ... funding handoff' implies this is a pre-payment step, and 'Never charges money by itself' implies it precedes a charge. But there is no explicit when-to-use vs when-not guidance relative to nexus_trade_create_checkout or nexus_trade_create_payment_intent.

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