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

With no annotations, the description carries the full burden and does well: it discloses the $5.00 charge, the 30-day window, the 5,000-call fair-use cap, the bearer-token return, and the /pass/x402 routing behavior. It stops short of stating how payment is actually settled, whether it auto-renews, or what happens when the call cap or 30 days is exhausted.

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-loaded with the offer and price, then the return value, then the usage rationale — a sensible order. The full route enumeration (feed, wallet-intel, TA, ...) is somewhat verbose given 'every paid route' already covers it, though it usefully ties back to the sibling tool names.

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?

No output schema exists, and the description compensates by explaining the returned bearer token and the exact Authorization header to use on subsequent calls. Only gap is post-purchase failure/expiry behavior, which an agent might need before committing $5.

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 schema has zero properties, so there is nothing for the description to disambiguate; baseline for a no-parameter tool is 4. The description correctly implies the only input is the act of purchase itself.

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 resource (Desk Pass) with concrete economics: one $5.00 payment for 30 days of access to every paid route, capped at 5,000 calls. The enumerated route list and the bearer-token return value make it unmistakable versus the sibling per-route tools like akari_feed or akari_ta.

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?

Explicitly names the trigger ('Use when an agent polls on a schedule') and quantifies the alternative: at $0.02/call, hourly polling costs $14.40/month, so the pass is the cheap path. The per-call route siblings are the named alternative, and the cost math supplies the when-not condition implicitly.

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