browser_about

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

With no annotations, the description carries the full burden and does well: it discloses that the tool produces clickable pre-filled URLs rather than submitting anything itself, and that the installations list is empty until the browser has been used in the chat. It doesn't explicitly say the call is side-effect-free or whether anything is transmitted externally.

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?

Purpose is front-loaded, but the second capability (installations listing) is buried in a long parenthetical sentence that also explains what BROWSER_MCP_PROFILE can choose — a detour unrelated to the primary feedback flow. The trigger list is efficient, but overall the text is longer than needed.

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?

With no output schema, the description does the required work of describing returns (submit_url plus an installations list with profile name, installation id and version) and the empty-list edge case. Most of what an agent needs to call and act on this tool is present, though the relationship to browser_provide_feedback remains unexplained.

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% and the schema already documents intent, title and body including the URL-encoding behavior and the 'info' default. The description restates the enum values ('intent="wish" | "use_case" | "bug" | "info"') without adding format or constraint detail beyond the schema, so baseline 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 first sentence names a concrete verb and resource (returns Browser MCP info and pre-filled submission URLs), and the later clause adds a second capability (listing connected installations with profile name, id and version). It is clear what the tool does, but it never distinguishes itself from the sibling browser_provide_feedback, which sounds like a near-neighbor.

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?

Gives explicit, enumerated trigger conditions (a)–(d) with example user phrasings ('I wish browser-mcp could...'), plus the instruction to call it PROACTIVELY and to offer the returned submit_url to the user. An agent knows exactly when to reach for this tool.

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