set_browser_config

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions setting configuration but doesn't explain whether this requires specific permissions, if changes are immediate or require restart, what happens to existing configuration, or any side effects. The example about viewport is helpful but insufficient for a tool with 7 parameters including security-related options like 'disable_web_security'.

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 brief (two sentences) but inefficiently structured. The second sentence is redundant with the tool name and could be more informative. While concise, it lacks proper front-loading of the most important information about what this tool actually configures.

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?

Given the tool has 7 parameters (including security-sensitive ones), no annotations, and 0% schema description coverage, the description is inadequate. It doesn't explain the scope of configuration, relationship to sibling tools like 'get_browser_config', or provide enough context for safe usage. The existence of an output schema helps but doesn't compensate for the missing behavioral and parameter context.

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 0%, so the description must compensate. It only mentions 'viewport_width' and 'viewport_height' parameters, ignoring the other 5 parameters including critical ones like 'session_id' (required), 'headless', 'no_sandbox', 'user_agent', and 'disable_web_security'. The description adds minimal value beyond what's in the schema titles.

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 the tool 'Set advanced browser configuration for a specific instance', which provides a clear verb ('Set') and resource ('browser configuration'). However, it doesn't distinguish this from sibling tools like 'get_browser_config' or explain what makes it 'advanced' versus basic configuration options available elsewhere.

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 provides minimal guidance with 'If you want to change the viewport, you can use the set_browser_config tool to change the viewport_width and viewport_height.' This gives one specific use case but doesn't explain when to use this versus other configuration methods, what other parameters are for, or any prerequisites. No alternatives or exclusions are mentioned.

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