Call this once before acting to retrieve setup guidance and available browser automation tools; use it to browse, fill forms, and navigate real Chrome.
START HERE. The listed tools: browse, find, act, page_slice, tabs, debug, guide. Call once before you act.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a one-time, presumably side-effect-free read via 'call once', but never states that it is read-only, what it returns, or whether it has any cost or auth requirement.
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?
Very brief and front-loaded with 'START HERE', which is exactly right. The enumeration of sibling tool names is somewhat redundant given they are already exposed, but it costs little.
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 parameterless, output-schema-less orientation tool, the description is thin: it tells the agent to call it but not what the returned guidance contains, so the agent cannot anticipate its value beyond 'read this first'.
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 tool takes zero parameters, so there is no parameter semantics to document; the baseline of 4 applies and no schema gap exists to compensate for.
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 positions the tool as an entry point ('START HERE', 'guide'), which does distinguish it from the action-oriented siblings. However, it never states what the tool actually returns or what kind of guidance it provides, and the enumerated tool list largely restates the sibling names already visible to the agent.
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?
'Call once before you act' gives an explicit, actionable trigger for invocation and implies it should not be repeated. It stops short of any when-not guidance or explanation of what happens if you skip it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.