Get Page Content (text + optional screenshot)

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

Annotations already mark readOnlyHint=true, so description doesn't need to emphasize safety. It adds context about screenshot benefits but does not cover potential limitations like page load timing or character limits beyond the default.

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?

Extremely concise: three short sentences plus parameter docs. Front-loaded with core purpose, then usage note, then parameter details. No fluff.

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?

Covers all critical aspects: what it reads, optional image, usage guidance, and parameter meanings. Lacks output format description, but given no output schema and simple read operation, it is reasonably complete.

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 has 0% coverage, but description compensates by explaining include_screenshot's purpose and specifying max_chars as max characters. This adds meaningful guidance beyond the schema's type and default.

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?

The description clearly states the verb 'Read' and the resource 'current page's text content', with an optional screenshot. It distinguishes itself from sibling tools like gv_screenshot and gv_get_page_links by specifying the exact scope.

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 explicit guidance on when to set include_screenshot=true (captcha, image buttons, complex visual structure). However, it does not directly contrast with alternatives like gv_screenshot for standalone image capture, missing a clear 'when not to use'.

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