ebay_get_payments_program_onboarding

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

No annotations are provided, so the description must supply behavioral insights. It only mentions deprecation and required scopes, omitting details on safety, idempotency, rate limits, or errors. This is insufficient for a tool with no additional structured metadata.

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 concise at two sentences, front-loading the core purpose and then adding the deprecation note. It could be slightly more structured, but the brevity is effective.

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 should clarify what the tool returns. It only says 'onboarding information,' which is vague. Given the deprecation and lack of return specification, the description is incomplete for agent decision-making.

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 input schema has 100% description coverage, with both parameters explained. The tool description adds no extra semantic value beyond what is already in the schema, so a baseline score of 3 is appropriate.

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 clearly states 'Get payments program onboarding information,' which identifies the verb and resource. The deprecation note provides context, but it does not explicitly differentiate from siblings like ebay_get_payments_program or ebay_get_payments_program_status.

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 deprecation warning informs agents when not to use the tool, and the OAuth scope requirements are included. However, there is no explicit statement of when to use it nor mention of alternative tools for the current functionality.

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