browser_start

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions launching or reconnecting Chrome but does not explain implications of reconnection, side effects, authentication needs, or what happens with the headless parameter. The description lacks depth for safe agent usage.

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 concise, consisting of two short sentences. Every sentence adds value: the first states the tool's action, the second gives an essential usage hint. No unnecessary words, perfectly front-loaded.

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 simplicity (one optional parameter, no annotations) and existence of an output schema, the description is minimal but covers the core action and ordering requirement. However, it fails to explain the headless parameter or the reconnection behavior, leaving gaps for an agent. It is adequate but not complete.

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%, and the description does not mention the 'headless' parameter at all. It adds no meaning beyond the schema's type definition. The agent receives no guidance on how or why to set headless mode, which is critical for a start tool.

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 launches or reconnects Chrome with CDP, specifying the verb 'lanza' (launch) and resource 'Chrome con CDP'. It distinguishes from sibling tools by indicating it must be called before any others, which implies it is the initialization step.

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 explicitly states 'Debe llamarse antes que las demas tools' (must be called before the other tools), providing clear context for when to use this tool. However, it does not mention when not to use it or provide alternatives, but the context of sibling tools makes the purpose evident.

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