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

With no annotations, the description carries the full burden and does substantial work: it discloses the atomic post-and-execute semantics, the two payment rails (Stripe card / USDC Tempo), the specific -32042 failure mode, and the required retry handshake. It stops short of covering idempotency, whether a task row persists on payment failure, or rate limits.

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?

Front-loads the core purpose, then the payment mechanics and recovery path in three dense sentences with no filler. The parentheticals are load-bearing rather than decorative, though the payment clause is information-heavy.

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 payment-gated mutation with no annotations and no output schema, the description covers the operation, cost model, and failure/retry flow, and notes that the caller receives the result. The return payload shape and edge cases on partial failure remain unspecified, but the caller's next action is always clear.

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 the baseline is 3, but the description adds meaning beyond the schema for `credential`: it explains that the challenge comes back in the -32042 error and the proof can also be passed via params._meta['org.paymentauth/credential'], which the schema does not convey.

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?

States a specific verb pair and resource ('Post AND execute a task atomically') and clarifies the distinguishing behavior ('the worker runs now and you get the result'). This implicitly separates it from the sibling sidequest_post_task, though it never names that alternative explicitly.

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?

Provides real procedural guidance for the payment branch (without a credential you get -32042, then retry with the echoed challenge). However, it never states when to choose run_task over the sibling sidequest_post_task, leaving the core selection decision to inference from 'atomically'.

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