Post Instances Payouts Stellar

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

Annotations already declare that this is a non-read-only, non-destructive, open-world operation, so the safety profile is partly covered. The description adds no behavioral context, such as fund-movement implications, authorization requirements, or how idempotency should be applied.

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?

It is a single front-loaded sentence with no wasted words. However, it is under-specified rather than appropriately sized for a complex payout-creation operation.

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 funds-moving payout tool with nested parameters, optional idempotency, and multiple wallet/signing modes, the description is far too sparse. Annotations provide some safety context, but the definition still leaves the agent without necessary operational guidance.

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 description contributes no parameter meaning at all. With only 33% schema description coverage and a nested request body containing key fields like quote_id, signed_transaction, wallet_id, and sender_wallet_address, the description fails to compensate for the low coverage.

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 verb and resource ('Create Payout') plus the network ('Stellar'), so it is clearly distinguishable from EVM/Solana payout siblings. It does not, however, distinguish this from the closely related StellarAuthorize sibling.

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?

There is no guidance on when to use this tool versus PostV1InstancesPayoutsStellarAuthorize or the other payout rail tools. It also does not mention prerequisites such as obtaining a quote_id or whether signing/authorization must happen first.

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