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

Annotations only declare it as non-read-only, non-idempotent, non-destructive; the description adds substantial context beyond them — the two-phase paid handshake, the need to retain session_id and secret, the required polling for an active state, and the warning that page content is untrusted data. It stops short of stating what happens on payment failure, whether a quote expires, or the cost/refund path, which is the remaining gap for a paid mutation.

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?

Four short sentences, front-loaded with the purchase action and options, followed by the payment protocol, credential-retention warning, and the safety note. Every sentence carries a distinct instruction; nothing is repeated filler.

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 does tell the agent what comes back (session_id and secret) and what to do with it (keep it, poll get_session). What is missing is any indication of the quote's shape or cost and the failure/expiry behavior, which for a paid provisioning tool leaves a small but real gap.

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 only 43%, and the description only reinforces duration options, the honest default, and the _meta payment carrier (which is not even listed in the schema properties — genuinely useful added meaning). It says nothing about locale, timezone, viewport_width/height, or start_url beyond the schema's own one-liners, so it does not fully compensate for the coverage gap.

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 and resource ('Buy a browser session') plus the concrete options ('10m, 30m or 60m'), which immediately distinguishes it from get_session, extend_session and close_session. An agent knows this is the provisioning/purchase step of the lifecycle, not a read or a mutation of an existing session.

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?

Gives an explicit call sequence: first without payment for the x402 quote, then again with the signed payment in _meta, then poll get_session until state is active before browsing. It names the sibling to use next and the precondition that must hold before any other tool (navigate, act) is safe to call.

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