payoutMethods.update

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

With no annotations provided, the description carries the full burden. While 'Update' implies mutation, the description fails to disclose whether this is a partial or full replacement, what validation occurs on the bankAccount object, or error conditions like missing payout method IDs.

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 brief (4 words) and front-loaded, but given the complexity of the nested input schema with four parameters, this is under-specified rather than appropriately concise. However, it contains no redundant or wasted words.

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 financial mutation tool with complex nested parameters (bankAccount.address), zero schema coverage, no annotations, and no output schema, the description provides insufficient context to safely invoke the tool.

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 0%, yet the description lists no parameters or their semantics. It does not explain the relationship between accountId and payoutMethodId, nor the structure of the nested bankAccount object (which contains address sub-objects), leaving all four parameters undocumented.

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 the verb (Update) and resource (Ryft payout method), but fails to differentiate from siblings such as payoutMethods.create or paymentMethods.update, and does not clarify what constitutes a 'payout method' in this context.

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?

No guidance provided on when to use this tool versus alternatives (e.g., create vs update), nor any mention of prerequisites like existing payout method verification or account requirements.

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