Get browser page URL

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

The description discloses that there is no global current page, a behavioral trait not covered by annotations. It also reinforces the read-only nature implied by the annotations without contradicting them.

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 concise and well-structured, consisting of two clear sentences that directly convey the necessary information without redundancy.

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?

The description does not specify the return value or potential error conditions, but for a simple read operation with readOnly and idempotent annotations, it may be sufficiently complete for typical use.

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?

The description hints at the need for sessionId and pageId by mentioning 'IDs returned for the intended session', but it does not explain timeoutMs. Since the schema provides no parameter descriptions, the description only partially compensates.

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 that the tool reads the current URL of a specific page and explicitly requires addressing. It distinguishes itself from any global current page concept, making the purpose unambiguous.

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?

It provides guidance that IDs are necessary because there is no global current page, but it does not explicitly contrast with alternative tools or specify when to choose this over other navigation or read operations.

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