browser_chat

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Natural language browser control' with no information about side effects, permissions, scope of actions, or whether it modifies browser state. This is completely insufficient for an agent to anticipate consequences.

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 extremely short, but that brevity reflects under-specification rather than efficiency. It omits essential information about what the tool does and how it works, making it an underspecified placeholder rather than a concise, informative definition.

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 large sibling set and no annotations or output schema, this description is grossly inadequate. An agent cannot determine the tool's purpose, inputs, or expected behavior, making it impossible to use correctly without external knowledge.

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 covers 100% of parameters with descriptions ('Session name' and 'Natural language instruction'), so baseline is 3. The description adds no additional semantic meaning beyond what the schema already provides, so it remains at baseline 3.

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 'Natural language browser control' states a resource (browser) and a general capability (control) but is too vague to indicate the specific function. It does not distinguish this tool from the many specific sibling tools like browser_navigate or browser_click, making it hard for an agent to select this tool over others.

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?

No guidance on when to use this tool versus alternatives. With over 30 sibling tools covering specific actions, the description gives no conditions or exclusions. An agent cannot tell if this tool should be used for complex multi-step instructions or if it's a fallback for other tools.

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