ebay_get_payment_policies

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

Annotations already declare readOnlyHint=true, and the description only restates the read nature with 'Get'. It adds no additional behavioral context such as pagination, result limits, data scope, or seller authorization requirements. With annotations present, the description contributes almost nothing beyond the structured data.

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 a single efficient sentence with no filler, and the core action and resource are front-loaded. It is appropriately concise, though it sacrifices useful usage context for brevity.

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 simple one-parameter read-only tool, the description is minimally viable: an agent can infer the resource and action. However, it lacks sibling differentiation and does not clarify that this returns all policies rather than a single policy, leaving some contextual ambiguity despite the plural name.

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 schema covers 100% of the single parameter with a clear description ('eBay marketplace ID') and an enum of valid values. Since schema coverage is high, the baseline of 3 applies; the description adds no extra parameter-level meaning.

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 clear verb and resource: 'Get payment policies for the seller'. It is immediately understandable as a read operation returning payment policy data. However, it does not differentiate itself from the sibling tools ebay_get_payment_policy and ebay_get_payment_policy_by_name, aside from the plural/aggregate implication in the name.

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?

No guidance is provided about when to use this aggregate 'get policies' call versus the singular ebay_get_payment_policy or ebay_get_payment_policy_by_name. There is no mention of prerequisites, alternatives, or exclusions, so an agent must infer the appropriate context from the tool name alone.

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