ebay_create_custom_policy

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

The readOnlyHint=false annotation already flags this as a mutating operation, and the description says 'Create' consistently. However, the description adds no extra behavioral context, such as whether a policy ID is returned, whether creation can overwrite an existing policy, or what validation or failure behavior to expect.

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, clean sentence with no filler and the action front-loaded. It is concise, though slightly under-specified in content.

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 tool with a nested required object, no output schema, and no parameter descriptions, this description is too thin. It does not explain what a valid custom policy requires, what constitutes a policy type, or what the agent should expect after calling it.

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 has 0% description coverage, and the description does not mention the required 'policy' object or its required 'name' and 'policyType' fields. The agent is left to infer meaning from field names alone, with no guidance on allowed or expected values for 'policyType'.

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: 'Create' a 'custom policy'. It does not differentiate custom policies from the many sibling policy-creation tools (e.g., create_fulfillment_policy, create_payment_policy), but the core purpose is unambiguous.

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 use this tool, what prerequisites exist, or which sibling tools to prefer. The agent is not told how this relates to ebay_get_custom_policy, ebay_update_custom_policy, or the other create_*_policy tools.

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