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

The description describes a mutating, billable operation – it starts up to 100 runs and 'Charges 0.05 XNO per run via x402' – while annotations declare readOnlyHint=true and idempotentHint=true. Starting jobs and deducting XNO per call is neither read-only nor idempotent (a second call charges again), so the description directly contradicts the structured safety profile.

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?

Two dense sentences, front-loaded with the capability, then cost model, then the return-and-poll workflow. No filler; every clause carries information an agent needs.

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 described, and the description still covers cost, parallelism, immediate job-id return, and the free polling step. The one gap is that it never reconciles its billing/write behavior with the read-only annotations it is paired with, leaving the agent's safety assumptions unresolved.

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?

Only one parameter and schema coverage is 100% – the schema already defines 'runs' as a JSON list of 1-100 {task, website} objects. The description reinforces the upper bound and notes price scales with run count, but adds no syntax or format detail beyond the schema; the baseline 3 applies.

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+resource+scale: 'Start up to 100 browser-agent runs at once, in parallel on isolated browser contexts.' An agent can immediately distinguish this batching tool from the singular browser_agent sibling and understands the isolated-context execution model.

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 useful workflow context ('Returns every job id immediately; poll each via its links.status (free)') but never explicitly states when to choose this over the singular browser_agent or what conditions favor batching. Usage is implied by 'up to 100... at once' rather than spelled out.

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