grant_browser_access

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

Discloses that the tool writes a permission flag, which is a side effect not captured in the annotations. It also emphasizes the consent requirement, adding context about authorization. This is valuable transparency beyond the raw hints.

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?

Two sentences, front-loaded with the main purpose, and directly followed by the critical usage constraint. Every sentence earns its place—no fluff or repetition.

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 zero-parameter, no-output-schema tool, this description is complete. It tells the agent what the tool does, when it may be called, what it does internally, and the resulting effect. No missing information is needed for correct and safe invocation.

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?

There are zero parameters, so the schema is trivially covered. The description adds nothing about parameters because none exist. Baseline for 0 params is 4, and the description provides no unnecessary detail.

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's purpose: granting the agent permission to control the user's browser. This is a specific verb+resource combination that distinguishes it from all sibling tools, which are either system monitoring, file operations, or browser actions themselves (e.g., browser_open_url).

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?

Explicitly states the only condition for use: after the user has explicitly said yes/granted/allow. It also explains the consequence of use (subsequent browser_* calls will then work), giving clear when-to-use guidance and implying it should precede any browser_* calls.

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