spraay_batch_estimate

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

The description adds clarity beyond annotations by stating it's an estimate (non-mutating despite readOnlyHint=false), returning gas in wei and USD, and costing $0.001 USDC. No contradiction with 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 two concise sentences, front-loaded with purpose and immediately followed by return and cost details. No 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?

Given an output schema exists, the description is fairly complete, covering the return type and cost. Could mention prerequisites like having a funded wallet or chain context, but not critical.

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 coverage is 100%, so baseline is 3. The description does not add additional meaning to the parameters beyond what the schema already provides (token default, recipientCount range).

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 clearly states it estimates gas cost for a batch payment, with specific verb 'estimate' and resource. However, it does not explicitly differentiate from other estimate tools like spraay_stellar_estimate or spraay_free_estimate_batch, which are for different contexts.

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?

It implies usage before executing a batch payment ('before executing') and mentions a cost of $0.001 USDC, but does not provide explicit when-to-use/when-not-to-use guidance or mention alternatives like spraay_batch_execute.

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