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

The description discloses financial settlement ('may settle USDC'), the need for spending approval, and the resulting task_token with seven-day access. This goes beyond annotations by adding risk and post-success behavior, though it does not mention idempotent retry semantics already captured by 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?

Three sentences, action-first, and includes essential warnings without any waste. Every sentence earns its place.

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?

Covers prerequisites, side effects, and post-action token handling. Lacks explicit error/retry guidance, but the output schema and annotations help fill some gaps, making it sufficiently complete for a payment tool.

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 adds value by emphasizing that users/mode must exactly match get_direct_crawl_payment, reinforcing the contract, and provides protocol context for payment_signature_b64.

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 an action: submitting an x402 v2 PAYMENT-SIGNATURE that may settle USDC and create a crawl task. It distinguishes from siblings by tying to get_direct_crawl_payment and the accountless crawl concept.

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 provides an explicit precondition: 'Call only after explicit spending approval.' It also references get_direct_crawl_payment for the exact users/mode, signaling when to use. However, it does not explicitly exclude alternative tools like create_crawl_task.

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