SellerWallet_deleteScheduleTransaction

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

With no annotations, the description carries the transparency burden. It does disclose that this is a catalog entry running in the user's Kuudo deployment and that it performs a deletion. However, it does not disclose irreversibility, permission requirements, or downstream effects beyond the deletion itself.

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 compact and free of fluff. The execution-context note and the action statement each add necessary information without redundant wording.

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 destructive operation, the description lacks the target-identification mechanism and any indication of return behavior or failure effects. The schema and output-schema are empty, so the description needed to compensate more than it does; an agent could not confidently invoke this tool correctly.

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 schema declares zero properties and allows additional properties, so there is nominally nothing to document. However, a delete operation logically needs some way to identify which scheduled transaction to delete, and the description provides no guidance on any identifier or argument. This ambiguity makes the otherwise high schema coverage insufficient.

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 states a specific action ('Delete') and a specific resource ('a transaction request that is scheduled from Amazon Seller Wallet account to another customer-provided account'). This is clearly distinct from the other SellerWallet sibling tools, none of which delete scheduled transaction requests.

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 makes the usage context clear: it is used to delete a scheduled Seller Wallet transaction request, and it notes that the operation runs in the Kuudo deployment rather than in the current environment. It does not explicitly compare against alternatives, but the delete action is unique among the SellerWallet siblings.

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