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

Adds substantial context beyond the annotations: the session is a real Chrome authenticated as the user (auth/session implications the hints do not convey), navigation is restricted to Google Discover pages despite openWorldHint, and it returns the visible elements and text using the same numbering as the other browser tools. That return-shape note matters because there is no output schema.

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?

Compact and front-loaded with the action, with the sequencing rule immediately after. The phrase 'with the same numbers' is slightly cryptic and only resolves once the agent has seen the sibling browser tools, which costs a bit of standalone clarity.

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 one-parameter tool with no output schema, the description covers the action, the ordering, the scope restriction, the authentication context, and the shape of the response. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds a real constraint the schema lacks: only Google Discover pages will open, which qualifies the schema's generic 'public http or https address' example.

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?

States a specific verb and resource: it starts the user's Google Discover Cloud Browser (a real Chrome signed in as the user) and opens `url`. It also distinguishes itself from the surrounding browser tools by saying it must be called first and is for what the Google Discover tools do not cover.

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?

Gives explicit ordering ('Call it first'), an explicit scope limit ('Only Google Discover pages open'), and an explicit fallback rule ('use it for what the Google Discover tools do not cover'). An agent can decide between this, cotlet_browser_navigate, and the Discover card tools without opening schemas.

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