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

With no annotations, the description carries the full burden and does so: it discloses that the tool does not navigate, that it emits a NAV_OFFER tag rendered as a clickable button, and that the user must click to actually navigate. That is the key behavioral trait an agent needs to avoid falsely telling a user they were moved.

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?

Front-loaded with the critical warning, then scoped by rules, then the page reference. The structure is excellent, but the bulleted page list largely repeats the enum already present in the schema, adding bulk without new routing information beyond the category grouping.

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 and no annotations, yet the description explains the return mechanism (NAV_OFFER tag rendered as a button) and the full callable surface. Nothing an agent needs to select and invoke this tool correctly is missing.

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% and the enum already documents every allowed page value, so the baseline is 3. The description adds value beyond the schema by grouping the values into semantic categories (MARKETING, DASHBOARD, EDITOR, ADMIN, etc.), which helps intent matching, though it does not explain value formatting since the values are opaque identifiers.

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 ('Get information about a page and provide a clickable link') and explicitly distinguishes itself from the sibling navigate_to_page, including the exact phrasing that selects the other tool. An agent can route between the two without opening either schema.

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 DO NOT USE rule with quoted trigger phrases, names the alternative tool and what it does, then enumerates three concrete USE-only scenarios. This is the textbook when/when-not/alternative structure.

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