browser_get_text

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

The description only states 'Get text content' implying a read operation, but with no annotations, it fails to disclose behavioral details like whether the tool waits for the element, what happens if the element is missing, or if the text includes hidden elements.

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 very concise (one sentence plus a reference), which is efficient. However, it may be too minimal, bordering on under-specification. The front-loading is good.

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?

Given the tool's simplicity (1 param, no output schema), the description lacks essential details like return format, error behavior, and handling of multiple elements. The reference to browser_docs partially compensates but does not make it 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?

The schema covers the single parameter 'selector' with a clear description 'Playwright selector for the element'. The tool description adds no extra meaning beyond this, so baseline 3 is appropriate.

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 it retrieves text from an element via selector. The verb 'Get' and resource 'text content' are specific, and the tool is distinguishable from siblings like browser_get_dom (DOM structure) and browser_read_page (full page).

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 usage guidelines provided. The description does not indicate when to use this tool vs alternatives (e.g., browser_get_dom or browser_read_page), nor does it mention prerequisites or constraints.

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