perch_navigate

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

With no annotations, the description carries the full burden, and it does most of the work: it discloses that navigation is top-level only, that it waits for a Cloudflare challenge to clear, and that the editor must be reloaded afterward. It does not say whether navigating away discards current editor state, what the tool returns, or what failure looks like if the challenge never clears.

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 primary purpose is front-loaded, and the recovery procedure is sequenced clearly (visit top-level, let challenge clear, perch_start with force:true). The middle sentence is dense and runs long, but nearly every clause carries actionable information rather than filler.

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?

For a two-parameter tool with no annotations and no output schema, the description supplies the essential context: scope (top-level only), the CF challenge behavior, and the recovery workflow. The remaining gap is the effect on existing editor/page state and error behavior when the challenge does not clear.

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 100%, so url and timeout are already documented in the schema. The description restates the challenge-wait semantics that the timeout parameter description already carries, adding no new syntax or format detail beyond that. Baseline 3 is appropriate.

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 and resource: navigate the whole editor PAGE to an https:// URL at top level. It also implicitly distinguishes itself from perch_start by positioning navigation as the recovery step that precedes a forced reload, so an agent can separate it from siblings without reading schemas.

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?

Gives an explicit when-to-use scenario (CF-blocked embed/subframe such as text-generation.perchance.org under ai-text-plugin) and the follow-up alternative (perch_start with force:true), plus the secondary case of loading pages for inspection. It omits any when-not guidance, e.g. preferring subframe-level navigation or when perch_refresh is the better choice.

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