payoutMethods.delete

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

No annotations are provided, yet the description fails to disclose critical behavioral traits for a destructive operation: it omits whether deletion is permanent, immediate, or asynchronous, and whether it affects pending payouts or requires specific account permissions.

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?

While the single sentence is not verbose, it is inappropriately brief for a destructive financial operation with undocumented parameters; the description undershoots the necessary detail level.

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?

Inadequate for a destructive tool: no annotations cover safety, no output schema is described, parameters lack documentation, and there are no warnings about side effects or required verification steps.

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 0% schema description coverage, the description must compensate by documenting the required 'accountId' and 'payoutMethodId' parameters, but it mentions neither their existence nor their semantics (e.g., UUID formats, lookup scopes).

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 specific verb (Delete) and resource (Ryft payout method), but lacks differentiation from the similar sibling 'paymentMethods.delete' and omits scope details like whether deletion is permanent or immediate.

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., account status), or warnings about irreversible consequences.

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