browser_navigate

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It fails to mention whether navigation waits for page load, how it affects the session state, whether it returns any result, or if it can fail (e.g., no history to go back). The terse phrase gives no behavioral context.

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 three words, which is efficient but arguably too sparse to be useful. It is front-loaded but fails to include necessary context, making it less 'appropriate' in size despite its brevity.

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 tool with two parameters and no output schema, the description is incomplete. It does not explain the expected values for 'direction', whether 'session' is optional/required, or what side effects occur. An agent cannot confidently call this tool correctly based on the given description.

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 100%, so parameters are documented (though minimally). The description hints that 'direction' might accept values like 'back', 'forward', or 'reload', but does not explicitly define them. It adds a small amount of semantic value beyond the schema's generic 'Navigation direction', but does not fully clarify allowable values or the role of 'session'.

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 'Back/forward/reload' indicates the tool performs browser navigation actions, conveying a specific purpose but lacking a clear verb+resource structure. It distinguishes from siblings like browser_open (which loads URLs) but is vague about the exact mechanism and doesn't fully differentiate from other navigation-related tools.

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 provides no guidance on when to use this tool versus alternatives like browser_open or browser_wait. There is no mention of prerequisites, typical use cases, or conditions under which navigation would apply, leaving the agent to infer usage.

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