spraay_stellar_batch

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

Annotations indicate readOnlyHint=false (mutation) and openWorldHint=true, but the description only adds cost ($0.02 USDC per call). It does not explain side effects, like blockchain transaction finality, failure modes, or that sourceSecret is sensitive. The description adds minimal behavioral context beyond annotations.

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 very short (2 sentences) and front-loads the purpose. It is concise but lacks structure, making it less scannable. Every word earns its place, but no additional structure is provided.

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?

Given that this is a payment tool with side effects and a required private key, the description is incomplete. It does not mention batch limits, source of funds, return format (though output schema exists), or error handling. The agent needs more context to use this tool safely.

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 descriptions are tautological ('amounts parameter', 'recipients parameter', 'sourceSecret parameter'), and the tool description adds no meaning beyond 'Provide the listed fields'. The agent cannot infer that sourceSecret is a private key, amounts are numbers, or recipients are addresses.

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 'Stellar batch payments', clearly indicating the tool performs batch payments on Stellar. This distinguishes it from siblings like spraay_stellar_estimate or spraay_batch_execute, but the purpose could be more explicit (e.g., 'Execute a batch of Stellar payments').

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 provides no guidance on when to use this tool vs alternatives like spraay_stellar_estimate or spraay_batch_execute. It does not mention prerequisites, batch size limits, or context for using this payment tool.

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