zen_click_and_wait_navigation

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

With no annotations, the description must disclose behavior. It reveals that the tool listens to tabs.onUpdated(status='complete') and is an atomic operation. However, it omits details on error handling, what happens if navigation does not occur, or timeout behavior, leaving some behavioral aspects unclear.

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: two sentences. The first sentence directly states the core functionality, and the second adds a comparative advantage and internal mechanism. Every sentence serves a purpose with no wasted words.

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?

While the tool is simple and the description covers the primary action and use case, it lacks parameter descriptions and fails to explain edge cases or expected outcomes. Given no output schema, additional guidance on return values or errors would enhance completeness.

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 input schema has 0% description coverage, so the description should clarify parameter meaning. It does not mention selector, timeout, or tab_id at all, providing no added semantic value beyond the bare schema.

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?

Description clearly states the tool clicks an element and waits for navigation. It explicitly distinguishes itself from two-step alternatives (zen_click + zen_wait_for_url) by claiming atomicity and reliability, effectively differentiating among many sibling 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 advises using this tool for links/submit buttons where navigation follows click, positioning it as a more reliable alternative to separate click and wait steps. It lacks explicit when-not-to-use or alternative scenarios, but provides clear context for its intended use case.

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