mobbin_navigate

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

No annotations are provided, so the description carries the transparency burden. It discloses the wait-for-load behavior, return values, and final URL (implying redirects). It does not mention session/auth requirements, but for a navigation tool this is a reasonable level of disclosure.

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?

First sentence is front-loaded and covers core purpose. The remainder is a verbose reference of URL patterns, but each section is labeled and useful; it is long yet not redundant.

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 exists, but the description explicitly states return values (page title and final URL). It also gives complete URL-construction guidance, making the tool usable with the parameter alone.

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 only says 'Full Mobbin URL'. Description adds extensive URL patterns, category-specific endpoints, and detail URL format, greatly enriching parameter meaning beyond 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 opens with a specific verb and resource: 'Navigate to a Mobbin URL'. It clearly states the action and what it returns, distinguishing it from sibling tools like mobbin_click or mobbin_scroll.

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 clear context by listing known valid URL patterns and screen/flow categories, implicitly guiding when navigation is appropriate. However, it does not explicitly name alternatives or exclusion criteria.

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