browser_about

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states that the tool returns info and pre-filled URLs, and it instructs the agent to 'offer' the submit_url rather than auto-submitting, implying a non-destructive informational operation. It could explicitly mention no side effects, but the behavior is transparent enough for this simple read-only tool.

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?

Four sentences, each earning its place: purpose, proactive triggers, invocation guidance, and community context. The most important action-oriented content is front-loaded, and the trigger list is detailed without being bloated.

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 simple tool with zero required parameters, no output schema, and no annotations, the description is complete. It explains what the tool returns, when to use it, how to map user intent to parameters, and what to do with the result. Nothing an agent needs to call it correctly is missing.

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 schema already fully explains all three parameters, including intent enum values and URL-encoding behavior. The description restates the intent values and briefly contextualizes title/body as pre-filled content, but adds no substantive new meaning beyond the schema.

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 and resource: 'Returns Browser MCP info and pre-filled URLs'. It also clearly enumerates the distinct intents (wish, use_case, bug, info), which distinguishes this tool from all browser-interaction siblings in the list.

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 gives explicit, concrete conditions (a–d) for when to call this tool proactively, including example user phrases. It also tells the agent exactly what to do with the output: pass an intent plus optional title/body and offer the returned submit_url to the user.

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