browser_navigate

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

With no annotations, the description must carry the full behavioral burden. It does disclose blocking behavior ('Aguarda o carregamento completo'), but it omits what happens on navigation failure, timeouts, or how wait_until changes the completion semantics — and 'aguarda o carregamento completo' is only true for the default 'load' value.

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?

Three short sentences, front-loaded with the action, then the sequencing rule, then the blocking behavior. No waste, though it is slightly terse relative to the undocumented parameters it leaves behind.

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?

No output schema and no annotations, so gaps cannot be waived. The description covers what the tool does and when to call it, but leaves an undocumented wait_until parameter and no error/return behavior, which an agent needs to call it reliably.

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 only 33%: task_description has a format note but url and the wait_until enum are undocumented in the schema, and the description says nothing about any parameter. It arguably adds a weak hint toward the load-wait default, but does not explain wait_until values or the required [AGENT-BROWSER-TASK] prefix.

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 states a specific verb and resource ('Navega para uma URL no browser'), and the sequencing rule ('sempre chame esta tool antes de interagir com qualquer página') implicitly separates it from browser_click/fill/read_page. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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 gives an explicit ordering constraint: call this before interacting with any page. That is actionable when-to-use guidance, but there are no when-not conditions and no mention of browser_wait_for, which is the most confusable alternative (wait for a condition vs. navigate-and-load).

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