browser_start

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

With no annotations and 23 parameters, the description fails to disclose important behavioral traits such as session lifecycle, resource management, or effects of parameters like 'humanize' or 'proxy'. Only mentions default headless Linux mode.

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 short but too brief for the tool's complexity. It front-loads the purpose but omits necessary detail, making it under-specified rather than efficiently concise.

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?

Despite having an output schema, the description lacks essential context about session usage, configuration options, and prerequisites. For a tool with 23 parameters, it is incomplete.

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 adds almost no meaning to the 23 parameters. Only the default mode gives a hint about 'headless' and possibly 'proxy', leaving the rest undocumented.

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 starts a 'CloakBrowser session' and notes the default mode. This distinguishes it from sibling tools that perform actions within a session.

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?

No guidance on when to use this tool versus alternatives, nor prerequisites. The description implies it's the entry point but does not explicitly state that a session must be started before other browser calls.

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