ebay_create_payment_policy

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

The readOnlyHint: false annotation already signals mutation, and the description only restates that the tool creates something. It adds no behavioral context beyond the annotation, such as side effects, authentication requirements, idempotency, or what the response contains.

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?

One short sentence is terse and front-loaded, but the brevity is under-specification rather than useful conciseness. It omits the structure of the nested policy object and leaves the agent to parse a deep schema unaided.

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 create operation with one deeply nested required parameter and no output schema, this description is too sparse. The agent is not told what a payment policy can contain, what constraints apply, or what the call returns.

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 0%, and the description says nothing about the required 'policy' object or its required fields (name, marketplaceId). With 0% schema coverage, the description must compensate, but it does not.

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 specific verb ("create") and a specific resource ("payment policy"), which separates it from sibling policy-creation tools such as ebay_create_return_policy or ebay_create_custom_policy. It is still essentially a restatement of the tool name and adds no additional defining detail.

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?

There is no guidance about when to choose this tool over the many sibling policy tools or what preconditions apply. The description does not say what kind of policy body is appropriate, what fields are needed, or when a payment policy should be used instead of a return/fulfillment/custom policy.

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