ebay_get_payout

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

Annotations only provide readOnlyHint=true. The description goes beyond that by disclosing three behavioral constraints the annotations cannot: the authorization scope, the EU/UK Digital Signature limitation (a hard blocker this server cannot satisfy), and the fact that the schema-referenced split payouts return 404. This is high-value context aligning with read-only behavior.

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?

Three tightly packed sentences: (1) what it returns, (2) how to find the ID, (3) prerequisites. Front-loaded with the action and result, zero 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?

With no output schema, the description enumerates the returned fields, and it covers the critical authorization and regional signature caveats. Complete for a single-resource getter.

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% and the schema already documents payoutId format patterns and marketplaceId defaults/enums. The description adds no syntax or format details beyond the schema, 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 ('Get'), resource ('one seller payout by payoutId'), API ('eBay Finances API') and enumerates returned fields (amount, status, instrument, transaction count). Clearly distinguishable from ebay_get_payouts (list) by the singular scope.

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?

Explicitly tells the agent how to obtain the required ID ('Find IDs with ebay_get_payouts'), names the required OAuth scope (sell.finances), and warns about the Digital Signature requirement for EU/UK sellers that this server does not fulfill. This is exactly the when-to-use / when-not context an agent needs.

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