browser_get_text

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

No annotations exist, so the description must fully disclose behavior. It only states the basic function without mentioning edge cases (e.g., element not found, hidden text, multiple matches) or returning plain vs rendered text. The agent lacks information about failure modes or output format beyond what the output schema provides.

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 concise sentence with no redundant information. Every word is necessary.

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 get-text tool with a likely output schema, the description is acceptable but could be more complete. It doesn't clarify behavior for multiple matches or non-existent elements, but given the tools's simplicity and the presence of an output schema, it meets minimum adequacy.

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 100% with each parameter already described (session_id, selector, by, max_length). The description adds no additional semantic value beyond what the schema provides, 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?

Description clearly states the action ('Get the text content') and the resource ('an element'). It effectively distinguishes this tool from sibling browser tools like browser_get_url, browser_get_page_source, and browser_get_element_attribute, which have distinct purposes.

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 from a specific element but provides no guidance on when to choose this over alternatives like browser_get_page_source (for full page text) or browser_get_element_attribute (for specific attributes). No explicit when-to-use or when-not-to-use context.

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