ebay_get_payout

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

Annotations only declare readOnlyHint=true, while the description adds crucial behavioral context: required OAuth scope, EU/UK digital-signature requirements, and the environment variables needed for signing. It also lists key payout fields returned, which helps the agent understand what the call provides.

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 three compact sentences with no filler, leading with what the tool returns and then covering ID sourcing and prerequisites. Every sentence contributes useful information.

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?

For a read-only financial lookup with no output schema, the description is complete enough: it names the returned fields, explains how to get the required ID, and discloses scope and signing prerequisites. Nothing essential for correct invocation appears missing.

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%, so both payoutId and marketplaceId are already well documented in the schema. The description adds little parameter-level meaning beyond noting that IDs come from ebay_get_payouts, which is already stated in the schema.

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 a specific verb and resource ('Get one seller payout') and identifies the source API and returned fields. It also distinguishes this single-payout tool from the sibling list tool by pointing to ebay_get_payouts for IDs.

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?

It clearly explains how to obtain the required payoutId via ebay_get_payouts and states the required sell.finances scope. It also gives the important EU/UK digital-signature prerequisite, though it does not explicitly state when not to use this tool versus every other sibling.

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