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

Annotations only declare safety flags, so the description carries the real behavioral burden and does so well: it discloses a per-call price ($0.005 USDC on Solana), the exact payment retry mechanism, and an HTTP equivalent for out-of-band use. It stops short of describing failure behavior for malformed expressions.

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 purpose and return value are front-loaded in the first clause, with payment mechanics following. The payment sentence is long but each clause is actionable; the HTTP URL is the only element that could be trimmed for some agents.

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?

With no output schema, the description correctly states what is returned (next 5 runs plus a human description), and the paid-call workflow is fully spelled out. Only error/invalid-expression behavior is left unspecified for this otherwise simple one-parameter utility.

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?

The single required parameter `expr` has 100% schema description coverage, so the schema already defines it. The description adds nothing about accepted cron dialects or field ranges, leaving the baseline 3 appropriate for a fully documented single-param tool.

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 (parse) and resource (cron expression) and even names the return content — next 5 runs plus a human-readable description. No sibling tool overlaps with this behavior, so the agent can select it unambiguously.

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 gives operational guidance for the payment handshake (call unpaid to receive the PaymentRequired challenge, then retry with the payment under _meta["x402/payment"]), which is genuinely useful. It gives no guidance on when to prefer this over alternatives or on preconditions such as expression syntax support, so usage is only implied.

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