get_page_info

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

With no annotations, the description carries the full behavioral burden. It accurately conveys a read-only operation by using 'Get' and explicitly lists the returned data. It does not discuss whether the browser state changes, but for a simple query tool the behavior is sufficiently transparent.

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, front-loaded sentence that wastes no words. It immediately states the verb and the full list of outputs, then closes with the unifying 'in one call' rationale.

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?

This is a simple, parameterless read-only tool with an output schema available, so the description does not need to explain return structures. The list of URL, title, origin, and navigation history fully scopes what the agent can expect in a single call.

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?

This tool has zero parameters, and the schema coverage is 100%, so no parameter documentation is needed. The baseline for zero-parameter tools is 4, and the description adds no misleading or unnecessary parameter details.

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 identifies the tool's function with a specific verb ('Get') and enumerates the exact resource pieces: current URL, title, origin, and navigation history. However, it does not explicitly differentiate itself from sibling tools like navigate_history or get_page_content, leaving some overlap ambiguous.

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 phrase 'in one call' implies this tool is meant for consolidating multiple page-info queries, giving a mild usage signal. It does not state when to avoid this tool or when to prefer a sibling like navigate_history, so the guidance is only implicit.

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