ebay_opt_out_of_program

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

With no annotations provided, the description bears full burden for behavioral transparency. It only states 'Opt-out of a seller program,' revealing nothing about irreversibility, permission requirements, side effects, or success indicators. This is severely insufficient for a write operation.

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, short sentence, making it very concise. However, it sacrifices necessary detail and is more under-specified than appropriately concise.

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 no output schema, no annotations, and a relatively simple parameter, the description should provide enough context for correct usage. It fails to do so, omitting important behavioral details and usage 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 coverage is 100% with one required parameter 'request' containing a nested 'programType' string. The description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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 'Opt-out of a seller program' clearly conveys the action as opting out, which is a specific verb-resource pair. It distinguishes from the sibling 'ebay_opt_in_to_program' and 'ebay_get_opted_in_programs'. However, it lacks specificity about which seller programs are applicable.

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, no prerequisites, and no indication of effects or confirmation steps. The sibling tools suggest a workflow (opt-in, check status), but the description gives no hints.

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