browser_detect_challenge

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

With no annotations, the description carries the full burden. It discloses the scan-and-notify behavior and the human-unlock trigger, but does not state whether the tool alters the page, requires prior attachment/authentication, or what form the notification signal takes.

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?

A single, front-loaded sentence conveys the core behavior and condition without redundancy. Every part contributes meaning, and the length is appropriate for this small tool.

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?

The tool is simple, but with no annotations and no output schema the description still leaves the required platform parameter unexplained and does not specify the return/notification format. It is adequate for gross selection but incomplete for confident invocation.

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% and the description never mentions the required platform parameter. The enum values hint at target e-commerce platforms, but the description does not explain how platform affects scanning or which value to choose.

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 action: scan open tabs for Captcha/OTP and emit a notification when human unlock is needed. It is clearly distinguishable in function from the ecommerce data/update siblings, though it does not explicitly name an alternative.

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?

The description implies when to use it: when a captcha/OTP is expected on open tabs and human intervention may be required. It gives no explicit exclusions or comparisons to siblings such as ecommerce_safety_guard, so the selection guidance is only implied.

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