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

Beyond the annotations (readOnly=false, idempotent=true, openWorld=false), the description discloses substantial operational context: it is a paid tool costing $0.25 in USDC on Base or Arbitrum One, requires an x402 v2 PAYMENT-SIGNATURE header, is invoked via POST to a specific paid_url, and that key custody stays with the caller. That meaningfully raises the bar above what the annotations provide, though rate limits and return shape are not discussed.

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 text is a dense run-on mixing useful facts (cost, payment mechanism, URLs) with unearned promotional asides such as 'Every trap — earned ourselves' and 'Your keys; custody never leaves you.' The seven steps are inlined as prose rather than front-loaded as a scannable list, so the signal-to-noise ratio is poor.

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?

An output schema exists, so return values need not be explained, and the description covers the invocation essentials: method (POST), payment protocol, price, accepted chains, and the paid URL. What an agent needs in order to call it correctly is largely present, with only minor gaps around failure/refund behavior.

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% and the single idempotency_key is fully documented in the schema itself, so the schema carries the burden. The description adds no parameter-level detail (format, uniqueness scope) beyond what is already structured, which matches the baseline 3 for high-coverage schemas.

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 eventually conveys that the tool delivers a 7-step machine guide for onboarding an agent to Farcaster, with the concrete sub-steps (bridge funding, FID registration, Ed25519 signer, EIP-712 domains, fname claim, profile, publish). However, the purpose is buried under marketing slogans and the title 'Compute History' does not match the name or body, which muddies selection. It never explicitly names or distinguishes itself from the obvious sibling nostr_kit.

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?

There is a loose implied condition ('Get an agent onto Farcaster'), but no explicit when-to-use, when-not-to-use, or named alternative. With 22 siblings, including nostr_kit and the agentid_* family, the absence of routing guidance leaves the agent guessing between near-duplicates.

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