chrome_navigate

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

With no annotations, the description bears the full burden of disclosing behavior. It only says 'wait briefly for the page to load,' which is vague and does not mention failure handling, return values, timeouts, or whether the tool blocks until navigation completes. This is insufficient behavioral disclosure for a navigation tool.

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 with no redundant information. Every word contributes to the core purpose, making it concise and easily scannable.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the one-sentence description is far from complete. It omits crucial context about tab selection, debug connection, matching criteria, and expected return behavior, leaving significant gaps for the agent.

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 0%, so the description must compensate by explaining parameters. It only vaguely maps 'url' and 'waitMs' ('wait briefly'), leaving tabId, debugUrl, urlContains, and titleContains entirely unexplained. The agent would not know how to set these parameters or what they do.

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 action ('Navigate'), the target ('the selected Chrome tab'), and the objective ('to a URL'). It also distinguishes itself from siblings like chrome_open_tab by specifying the selected tab, so the agent can tell this is for changing an existing tab's URL rather than opening a new one.

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 'selected Chrome tab' implies this tool should be used when a tab is already chosen and needs to be navigated, but it does not explicitly state when not to use it or mention alternatives like chrome_open_tab. Usage guidance is present but only implied rather than directly articulated.

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