scraping_browser_get_text

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

readOnlyHint=true already establishes this is a safe, non-mutating read, so the description needn't restate safety. It adds no further behavioral context, such as whether the output is truncated, whether it covers visible vs full DOM text, or how it differs from the HTML variant — leaving gaps the annotations do not fill.

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?

A single short sentence that leads with the verb and states the exact target. Nothing is padded, and the key qualifier ('text content', 'current page') is front-loaded.

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 no-parameter, no-annotation-burden tool with no output schema, the description is minimally adequate but leaves return-format questions open: an agent cannot tell if the result is plain text, includes markup, or is truncated. A sentence on what comes back would close the gap.

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?

The tool takes zero parameters, which sets the baseline at 4; there is no parameter syntax or meaning for the description to add or omit. Nothing here contradicts or misrepresents the empty 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 pairs a specific verb ('Get') with a precise resource ('the text content of the current page'), so the operation is unambiguous. It does not explicitly distinguish itself from close siblings like scraping_browser_get_html or scrape_as_markdown, but the 'text' qualifier does most of that work.

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?

There is no when-to-use guidance, no prerequisite statement, and no named alternative. The phrase 'current page' weakly implies the browser must already be on a page (via scraping_browser_navigate), but nothing tells the agent when to prefer this over get_html or snapshot.

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