Read text from the page

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

With no annotations provided, the description itself discloses that it returns visible text (not raw HTML) and that omitting the selector returns the whole page. This is useful behavioral nuance, though it does not address potential errors or edge cases like empty results.

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 description is a single, front-loaded sentence with no redundant information. It efficiently states the core behavior, the optional selector condition, and the intended purpose.

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 simple read-only tool with no output schema and no annotations, the description covers the essential purpose and behavior. It is complete enough for an agent to understand when and how to invoke it, though it does not describe return format or failure modes.

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 50%; the description clarifies the selector's optionality and behavior but does not mention max_chars. However, the schema provides default and maximum boundaries for max_chars, so the description adds only partial value beyond the 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?

The description clearly states the tool returns visible text of an element or the whole page, using a specific verb ('Return') and resource ('visible text'). It distinguishes itself from sibling browser tools like browser_screenshot (visual) and browser_evaluate (JavaScript execution).

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 phrase 'so the AI can read the current state of the panel' provides clear context for when to use this tool. It does not explicitly mention alternatives or exclusions, but the context is clear enough relative to the sibling set.

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