stealth_mode

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

Annotations indicate openWorldHint=true, meaning stateful behavior. The description mentions managing a browser and operations, but does not detail side effects or state persistence beyond the example. It adds some behavioral context but could be more explicit about state management.

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?

The description is concise (two sentences and an example) and front-loaded with the purpose. Every sentence is useful; there is no extraneous information.

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 has a complex nested schema and no output schema. The description explains the main operational flow but does not cover all configuration options in detail. Given the complexity, it is adequate but not comprehensive.

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 100%, so baseline is 3. The description adds value by providing a usage example and explaining the operation sequence, which aids understanding beyond the schema alone. It does not describe each parameter, but the schema already does.

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 clearly states the tool's purpose: bypassing bot detection systems like Cloudflare and Datadome. It distinguishes from siblings by specifying the use case and underlying technology (Playwright with anti-detection measures).

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 provides a clear usage sequence ('Start with operation: create_context then use the contextId') and an example. However, it does not explicitly state when not to use it or mention alternative tools for normal scraping, though the context implies it.

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