ebay_get_payments_program

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

With no annotations, description carries full burden. Discloses required OAuth scopes and deprecation, which is helpful. However, it does not mention side effects, rate limits, or error conditions. Basic transparency.

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 sentences, front-loaded with purpose, followed by deprecation and scope info. No unnecessary words. Efficient and well-structured.

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 low complexity (2 required params, no output schema, read operation), the description covers essential aspects: purpose, deprecation, and auth requirements. Lacks return value description, but output schema is absent. Adequate for the tool's simplicity.

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%, so baseline is 3. Description adds no additional parameter details beyond what is already in the schema (enum for marketplaceId, type for paymentsProgramType). Does not enhance understanding of parameters.

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 'Get payments program status for a marketplace', which is a specific verb+resource. Deprecation note adds context. However, it does not explicitly distinguish from sibling tools like ebay_get_payments_program_status or ebay_get_payments_program_onboarding, but the unique purpose is clear.

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?

Description mentions deprecation hinting that the tool may not be needed, but does not provide explicit guidance on when to use this tool versus alternatives. No when-not-to-use or alternative recommendations.

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