ebay_remove_post_order_document

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

The description is consistent with destructiveHint=true and adds valuable context beyond annotations: state restrictions, access enforcement, and the required commerce.post_order.document scope. No contradiction found.

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?

Three compact sentences with no filler: the core action is front-loaded, followed by state constraints and the permission requirement. Every sentence earns its place.

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 single-parameter destructive tool, the description adequately covers the operation, valid/invalid states, and permission requirements. It omits return/error behavior, but that is a minor gap at this complexity.

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?

With schema description coverage at 0%, the description provides no explanation of documentId. The parameter name is self-explanatory, but the description does not compensate for the missing schema documentation.

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?

States the exact action ('Delete'), the specific resource ('SUBMITTED post-order document'), and an explicit ineligibility condition for PUBLISHED documents. This clearly distinguishes it from related upload/download post-order document tools.

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?

Gives explicit state-based guidance: use it for SUBMITTED documents, and do not attempt it on PUBLISHED documents. It does not name sibling alternatives, but no direct alternative delete tool exists in the sibling set.

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