browser_stealth_mode

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

With no annotations, the description must carry the full behavioral burden. It discloses the specific overrides applied (navigator.webdriver, plugins, languages), which is more than a tautology, but it omits key behavioral traits such as persistence across tabs, effect on already-loaded pages, reversibility, and potential site breakage. Partial disclosure earns a 3.

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 a single front-loaded sentence with no wasted words, clearly starting with the action and then detailing the effect. It is appropriately sized for a simple toggle 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?

Given the tool's low complexity, 100% schema coverage, and absence of output schema, the description covers the basic function but leaves gaps in behavioral context (persistence, scope, interaction with related tools) that matter for correct invocation. It is minimally viable but not fully complete.

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 100%, and the single boolean parameter is fully documented in the schema including its default. The description does not add meaning beyond what the schema already provides, so the baseline of 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?

The description states a specific verb-resource pair ('Enable or disable comprehensive anti-detection stealth overrides') and gives concrete examples of what is masked (navigator.webdriver, plugins, languages). It does not differentiate itself from related siblings like browser_set_user_agent or browser_emulate_environment, which could also affect detection surfaces, so it falls short of a 5.

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?

There is no explicit guidance on when to use this tool, when not to, or which alternatives to prefer. The name and description imply usage, but an agent receives no context about prerequisites, interactions with other stealth-related tools, or scenarios where enabling stealth might be harmful.

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