browse

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

With no annotations, the description carries full burden. It discloses autonomy, resilience to layout changes, a step cap, and session reuse, which are useful. However, it does not warn about potential destructive actions (e.g., form submissions, purchases) or describe error/return behavior, which is a notable gap for a tool that interacts with live pages.

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 summary sentence is front-loaded, and the Args section is clearly structured with no redundancy. Every sentence adds value, including the resilience note and the capped step limit. It is appropriately sized for the tool's complexity.

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's moderate complexity and the presence of an output schema (which handles return values), the description covers core purpose, behavior, and all parameters. It could add more about behavior when max_steps is exceeded or error handling, but it is largely complete for an agent to use the tool correctly.

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 fully compensates by documenting all four parameters: task with an example, url as optional starting point, max_steps with a cap, and session_id for reuse. This goes well beyond the bare schema and provides complete semantic meaning.

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 it executes natural-language browser tasks via an autonomous agent, which distinguishes it from sibling tools that handle specific low-level actions like click or type_text. The verb 'execute' and resource 'browser task' are specific, and the mention of 'no CSS selectors needed' further differentiates it from tools that require selectors.

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 implies use for high-level, natural-language tasks with the example and the 'no CSS selectors needed' note, but it does not explicitly name alternatives or state when not to use this tool. It lacks clear exclusions or direct comparison with sibling tools like click or navigate.

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