Get element text

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

With no annotations, the description conveys a non-mutating read operation but omits details such as return format, selector matching rules (first vs all), and handling of hidden elements. This leaves significant behavioral ambiguity.

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?

Single sentence with precise language, no redundancy, and front-loads the action 'Read'.

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 tool, the description is adequate but does not explicitly state the return value or behavior for multiple matches, which is important given no output schema. Minor gaps remain.

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?

Only parameter 'selector' is described as a CSS selector in the description, adding meaning beyond the schema property name. However, no examples or selector syntax details are provided.

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 'text content of an element' with a CSS selector qualifier, distinguishing it from sibling tools like browser_click or browser_screenshot.

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 description implies usage for retrieving text but provides no explicit guidance on when to prefer this over browser_evaluate or limitations like first-match behavior. Context from siblings exists but is not leveraged.

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