scraping_browser_get_text

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

Annotations already declare readOnlyHint and destructiveHint=false, so safety is covered. The description adds no behavioral context of its own: it doesn't say whether text is visible-only, whether hidden/script text is included, whether output is truncated, or that results reflect the current DOM state after scrolling/waiting.

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 with the key qualifier ('of the current page') placed where it matters. It is efficient but so terse that it borders on under-specification rather than genuine conciseness.

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?

There is no output schema, so the description is the only place an agent could learn what comes back — format, length limits, whether markup is stripped — and it says none of that. Combined with the missing session prerequisite, an agent has to guess at the operational contract.

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, so there is nothing for the description to disambiguate or clarify. Baseline 4 applies.

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 the text content') scoped to 'the current page', which implies the live browser session rather than an arbitrary URL. However it never mentions how it relates to close siblings like scraping_browser_get_html or scrape_as_markdown, so an agent can't tell which text-extraction tool to pick from the name alone.

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?

No guidance on when to use this versus scrape_as_markdown, scrape_as_html, or scraping_browser_get_html, and no stated prerequisites. The critical precondition — that a page must already be loaded in the browser session via scraping_browser_navigate — is left entirely implicit.

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