ebay_get_payments_program_onboarding

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

No annotations provided, so description carries full burden. It discloses deprecation and OAuth scope requirements, but does not detail return value structure, error behavior, or rate limits. Minimal behavioral context.

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?

Very short, two sentences plus scope line. Front-loaded with purpose. No fluff, but could be more structured (e.g., separate sections).

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?

Given deprecation and no output schema, description lacks detail on what the onboarding information contains or how to interpret results. Minimal completeness for a tool that might still be called for legacy purposes.

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 coverage is 100%; both parameters have descriptions but description adds no extra meaning beyond the schema. paymentsProgramType has a generic description without enum values, so baseline 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?

Description clearly states it retrieves payments program onboarding information and notes deprecation. Verb and resource are specific, but does not differentiate from sibling tool ebay_get_payments_program.

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 states the method is deprecated and all sellers are already enabled, implying it should not be used. Provides required OAuth scopes. No alternative tool mentioned, but context is clear enough for an agent to avoid using it.

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