ebay_create_fulfillment_policy

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

With no annotations, the description carries the full burden for behavioral transparency. It only mentions OAuth scopes, which is useful but insufficient. It does not disclose whether the operation is idempotent, what happens if a policy with the same name exists, rate limits, or potential side effects.

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 very short (two sentences) and includes the OAuth scope, which is relevant. However, it sacrifices completeness for brevity. It could be restructured to front-load the main purpose and then provide key details without becoming 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 tool's high complexity (deeply nested policy object, no output schema, no annotations), the description is severely incomplete. It does not explain the return value, common errors, validation rules, or how the policy object should be structured. An agent would struggle to use this tool correctly without additional context.

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%, meaning the parameter schema provides no descriptions for its nested properties. The description does not add any explanation of what properties like 'handlingTime', 'shippingOptions', or 'categoryTypes' mean or how to use them. This forces the agent to rely solely on property names, which may be ambiguous.

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 clearly states 'Create a new fulfillment policy', which is a specific verb+resource combination. The tool name also helps distinguish it from other policy creation tools like ebay_create_return_policy and ebay_create_payment_policy. However, it does not elaborate on what a fulfillment policy entails, which could be clearer.

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?

The description provides no guidance on when to use this tool versus alternatives such as ebay_create_return_policy or ebay_create_payment_policy. It does not mention prerequisites, typical use cases, or how it fits into the broader workflow of listing items.

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