navigate_responsive_session

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description goes further by disclosing that contexts, cookies, and sizes are preserved across screens and that results are returned per screen with errors surfaced rather than hidden partial failures. That partial-failure disclosure is genuinely useful for a multi-screen mutation. It stops short of noting session prerequisites or side effects.

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 compact sentences with the core action front-loaded and no filler. The reload tip and the return-value sentence are each earning their place, though the third sentence is slightly informational rather than directive.

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?

With no output schema, the description correctly summarizes the return shape (per-screen results plus errors) and covers the session/url inputs adequately. Missing only minor detail such as expected failure modes or whether navigation is blocking across screens.

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 coverage is 50% (only sessionId is documented, and its lifecycle text duplicates the description's session context). The description compensates only lightly for the undocumented url parameter by noting that re-passing it triggers a reload, without adding format or constraint 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?

States a specific verb (navigate) and resource (all screens of a comparison) with a clear scope modifier (same URL, preserving contexts/cookies/sizes). It is distinguishable from siblings like observe_responsive_session or interact_responsive_session, though it never explicitly names or contrasts them.

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?

Provides one concrete usage hint -- re-pass the URL to reload all screens after changing code -- which implies when to call it again. However, it never states when to use this versus observe_responsive_session or interact_responsive_session, leaving the choice to inference.

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