browser_start

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

With no annotations, the description must carry behavioral disclosure. It usefully states that the session is visible, uses Edge IE mode, launches a new session, and does not attach to existing tabs, but it omits session lifecycle details, return behavior, and prerequisites such as whether Edge IE mode must be configured.

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 two short, front-loaded sentences with no filler. The core action comes first and the key limitation follows immediately.

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?

For a one-parameter launch tool, the description gives enough to understand the main action and the 'new session, not existing tab' constraint. However, with no annotations and no output schema, it should say more about what the tool returns or how the new session is referenced afterward.

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?

The single required url parameter has zero schema description coverage. The description implies that 'navigate' uses the url, but it does not explain accepted URL formats, whether full URLs are required, or what happens if the URL is invalid.

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: launch a new visible Edge IE mode session and navigate. It distinguishes itself from attaching to existing tabs, but does not explicitly contrast with close siblings such as browser_navigate or browser_open_page.

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 phrase 'Does not attach to existing tabs' gives a when-not condition, implying this tool is for starting a fresh session rather than reusing tabs. However, it does not explicitly say when to use browser_start versus browser_navigate, browser_open_page, or browser_sessions.

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