Hand blocked batch items to the person

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

Beyond the annotations, it discloses substantial behavior: waits up to waitMs per page (default 600000), reads a page only after the person interacts in its tab, requires local server plus remote debugging and a one-time Allow click, and explicitly states Octocrawl itself does not pass checks. It also documents the return shape.

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 core action and scoped tightly; every sentence carries information about timing, prerequisites, or return values. The long semicolon-chained sentences and dense clauses slightly reduce scannability.

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 supplies the return fields ({ id, handedOff, through, notThrough, items }) and covers prerequisites, timing defaults, and post-interaction behavior. An agent has everything needed to invoke it correctly.

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 description coverage is 0%, so the description must carry parameter meaning. It does explain waitMs well (default 600000, per-page wait, bounded by the schema's min/max), but the required 'id' parameter is never explicitly identified as the batch id — it is only inferable from 'a finished batch's items'.

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 states a specific verb and resource ('hand ... items that a check stopped to the person'), plus scope details ('one tab at a time', 'in their own Chrome'). It is clearly distinguishable from siblings like get_batch and wait_batch, which only report or wait on batches.

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 defines the triggering condition precisely — items flagged by a check (captcha, challenge, login wall) surfaced via get_batch's waitingForPerson — and states prerequisites: local server only, Chrome remote debugging enabled, person must click Allow once. It stops short of explicitly naming which sibling to use instead when no check is blocking.

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