browser_get_info

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

The description explicitly states what information is returned (URL, title). Although no annotations are provided, the tool has no parameters and is clearly a read-only getter, so the description adequately discloses its behavior.

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 a single sentence of 10 words, front-loading the purpose with no wasted words. It is optimally concise.

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 simple tool with no parameters and no output schema, the description sufficiently covers what the tool does and what it returns. It does not specify the return format, but the context is straightforward enough for an agent to use 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?

There are zero parameters, and the description adds no param information, but the baseline for 0 parameters is 4. The schema coverage is 100%, so no additional context is needed.

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 verb 'Get' and resource 'information about the current page', and specifies the exact pieces of information (URL, title). It distinguishes from sibling tools like browser_navigate or dom_click, which perform different actions.

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 that this tool should be used when the agent needs the URL or title of the current page. It does not explicitly mention when not to use it or alternatives, but the sibling tools cover other browser functions, making the usage context clear.

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