ebay_create_payment_policy

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

Without annotations, the description carries full burden for behavioral disclosure, but it only states the basic action. It does not reveal side effects (e.g., whether it replaces or adds to existing policies), required permissions, or constraints like marketplaceId being mandatory.

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 (one sentence), but it sacrifices useful information for brevity. It meets minimum efficiency but could include contextual hints without being verbose.

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 the complexity of the input schema (deeply nested object with many properties) and the absence of an output schema, the description fails to adequately inform an agent about the expected input structure, return value, or call behavior. It is incomplete for reliable tool invocation.

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?

Although schema coverage is 100% (the parameter 'policy' has a description 'Payment policy details'), the description adds no additional meaning beyond what the schema provides. The nested fields like deposit, immediatePay are not explained, so the agent must infer usage from schema alone.

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 'Create a new payment policy' clearly states the verb (create) and resource (payment policy), and it distinguishes this create tool from sibling tools like get, update, delete payment policy.

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 on when to use this tool (e.g., for setting up payment options for listings) or when not to use it (e.g., if a policy already exists). No alternatives or prerequisites are mentioned.

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