payouts.create

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

Without annotations, the description carries full burden. While 'Create' implies a write operation, it omits critical behavioral details: financial side effects, idempotency, async processing vs synchronous completion, cancellation policies, or required 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?

The single sentence is efficiently structured and front-loaded, but given the tool's complexity (5 parameters, nested objects, mutation), it is inappropriately brief rather than effectively concise.

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 complexity: no output schema, 0% parameter documentation, nested metadata object, and high-value mutation (financial payout). Description misses return value structure, error conditions, and currency handling.

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 has 0 description coverage and complex parameters (amount constraints, nested metadata object, 3-letter currency). Description mentions 'account' (mapping to accountId) but fails to document the other 4 required/optional parameters, units (cents?), or the critical payoutMethodId reference.

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 core action (Create) and resource (Ryft payout) with scope (for an account), but fails to distinguish from siblings like payouts.list or explain relationship to payoutMethods.create/transfer 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?

Provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., requiring a valid payoutMethodId from payoutMethods first), or exclusion criteria.

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