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

Goes well past the readOnlyHint/openWorldHint annotations: it discloses the 20,000-character truncation cap, that field values, cookies and storage are never returned, that long pages return content starting near the current scroll position, and the credit/timeout economics of the session. These are exactly the non-obvious traits an agent needs before calling.

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?

Four short sentences, front-loaded with what is returned, then exclusions, then pagination behavior, then cost. No restatement of the name or title and no 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?

With no output schema and no parameters, the description fully carries the burden: it describes the shape of the return value, the truncation and scroll-position semantics, the privacy exclusions, and session lifetime. An agent can call it correctly and interpret the result from this text 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?

Zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no param detail and instead spends its words on scope and return behavior.

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 (returns) and precisely enumerates the resource contents: readable text up to 20,000 characters plus a numbered list of links, buttons and fields. This clearly separates it from cotlet_browser_screenshot (visual capture) without needing to name it.

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 description implies the read-the-page role but never states when to choose it over siblings such as cotlet_browser_screenshot, cotlet_browser_navigate or cotlet_browser_scroll, nor when an agent should proceed to click/type. It also notes field values are never returned without saying where to get them, leaving an unresolved routing question.

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