spraay_sctp_pay

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

Discloses cost ($0.10 USDC per call), which is important behavioral info not in annotations. However, it does not describe what happens on success/failure, whether the operation is reversible, or any side effects beyond the cost.

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?

Two concise sentences, front-loaded with purpose and cost. Every sentence adds value with no redundancy.

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?

Lacks context about prerequisites (e.g., need for an invoice), behavior of the 'batch' parameter, and expected result format. Output schema likely covers return values, but for a payment tool, more guidance on use cases would be helpful.

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 parameters are already documented. The description adds no extra meaning beyond 'the listed fields as typed arguments,' which is merely a restatement. Baseline 3 is appropriate.

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 'Execute supplier payment.' This is a specific verb+resource, and it distinguishes the tool from sibling tools like spraay_sctp_invoice, spraay_sctp_po, etc. by focusing on the payment action.

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 on when to use this tool vs alternatives (e.g., when to use spraay_sctp_invoice vs this). No prerequisites or conditions are mentioned, leaving the agent without decision context.

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