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

With no annotations, the description carries the full burden, and it does disclose two genuinely useful traits: a confirmation flag is mandatory and unpaid steps return a 402 payment challenge. It says nothing about side effects, whether the run is mutating or idempotent, cost/rate limits, or what a completed run produces, which are large gaps for an execution-style tool.

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?

Three short sentences, front-loaded with the operation and immediately followed by the hard gating conditions and the failure code. Nothing is padded or redundant, though the terseness is partly the cause of the under-specification.

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 45-parameter, nested-object, no-annotation, no-output-schema tool, this is far too thin. It conveys only the entry conditions and one error signal; an agent must guess the semantics of nearly every input and has no picture of what a successful run returns.

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 description coverage is 0% across 45 parameters, many of them nested objects (ops, pay, rail, payout, solana, depotBilling). The description explains meaning for only four: confirm, demo, rider, and warrant. The remaining ~41 parameters, including high-impact ones like paid, rail, and delegation_mode, are undocumented in both the schema and the description.

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 expands the acronym and names the resource ('Run one ACN (Agent Commerce Network) run'), but 'run' is a nominalization that never explains what the operation actually performs. It gives no differentiation from close siblings such as spl_agentic_plan, spl_quote, or spl_discover, leaving the agent to infer which one starts work versus which plans it.

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 states invocation prerequisites ('Needs confirm:true plus demo:true or a rider+warrant pair'), which implies when the tool is callable and hints that spl_warrant_issue/reserve must come first. However, it never says when to choose this over spl_agentic_plan or the spl_warrant_* family, and no exclusions are given.

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