ebay_create_fulfillment_policy

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

No annotations provided, so the description carries full burden. It only states OAuth scopes, omitting behavioral traits like side effects, idempotency, or required fields beyond the schema.

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?

Very concise (two lines), front-loaded with purpose. However, it sacrifices necessary detail for brevity, making it less useful.

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 complex nested schema, missing annotations, no output schema, and many sibling tools, the description is incomplete. It lacks behavioral context, usage guidance, and parameter explanations.

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 description adds no explanation of the 'policy' parameter beyond the schema's minimal 'Fulfillment policy details'. Nested properties lack descriptions, and the description does not clarify their purpose or constraints.

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 explicitly states 'Create a new fulfillment policy,' clearly indicating the action and resource. It distinguishes from siblings like update, delete, and get, but does not explain what a fulfillment policy is relative to other policy types.

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 on when to create vs update, prerequisites, or why this tool over other create policy tools. Only OAuth scopes are mentioned, which are necessary but not sufficient for usage decisions.

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