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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it is scoped to the authenticated seller (no parameter to select one) and explicitly states that no KYC documents or bank details are returned, which is a meaningful privacy/data-exposure guarantee beyond the annotations.

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 short sentences, zero filler, with the core action front-loaded and the privacy caveat immediately after. Nothing is repeated from the title or schema.

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-value details need not be documented, and the annotations cover the safety profile. Combined with the zero-parameter shape and the privacy note, the description is sufficient to call the tool correctly, though it could have flagged the sibling onboarding tool for routing.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly signals that identity is derived from authentication rather than an input argument, which is the only semantic point that could be missed.

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 ('Read') and a precise resource ('the authenticated seller's Stripe Connect onboarding/payout readiness'), which distinguishes it from the write-side sibling nexus_trade_seller_connect_onboard. It does not explicitly name that sibling or other status tools (nexus_trade_settlement_status), so it stops short of a 5.

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 'the authenticated seller's' implies the usage context (must be called as a seller, no arguments needed), but there is no explicit when-to-use, when-not-to-use, or reference to alternatives such as the onboarding tool. Usage is implied rather than stated.

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