delete_policy

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose the core destructive action and the useful failure mode that eBay rejects deletion when listings are linked. Still, for a delete tool it does not state permanence/reversibility, permission requirements, or the dryRun default behavior, leaving meaningful gaps.

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 sentence with no filler. The core action is front-loaded and the critical eBay rejection caveat is included efficiently in parentheses.

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 simple two-parameter tool with full schema coverage, the description is nearly complete. It clearly states what the tool does and a major operational constraint. It could be improved by explicitly pointing to bulk_delete_policies for multi-policy deletion and by noting the destructive permanence, but these are minor for this complexity level.

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 100%, with policyId and dryRun already fully documented in the schema. The description adds no parameter-level detail beyond what the schema provides, so the 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 uses the specific verb '削除' (delete) and names the exact resource, '単体フルフィルメントポリシー' (single fulfillment policy). The '単体' qualifier clearly distinguishes it from the sibling bulk_delete_policies, and the parenthetical about eBay rejecting deletion when listings are linked adds precise scope.

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 '単体' qualifier signals this is for deleting one policy at a time, which implies bulk operations belong to bulk_delete_policies. It also states the key precondition/failure condition: deletion is rejected if there are linked listings. However, it does not explicitly name an alternative tool or give a direct 'use this when...' statement.

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