get_text

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

The term 'visible inner text' indicates that only visible text is returned, which is a behavioral trait beyond a simple read. However, it does not disclose behavior on missing elements, timing, or error handling. With no annotations, additional context would be beneficial.

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 a single sentence of 8 words, extremely concise and front-loaded. Every word is essential and no filler exists.

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 low complexity of the tool and the existence of an output schema, the description covers the core action. However, it lacks parameter guidance and usage context, which is needed due to zero schema coverage.

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 description coverage is 0%, yet the description adds no information about the two parameters (selector and session_id). The description does not explain what selector is or how session_id affects the call, leaving the agent to rely solely on parameter names.

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 'Get the visible inner text of an element' uses a specific verb (get) and resource (visible inner text of an element). It clearly distinguishes from sibling tools like get_attribute (attribute vs text) and get_dom (DOM structure vs text).

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 tool versus alternatives like get_attribute or execute_js. The description implies it's for visible text, but does not explicitly state that other tools are better for hidden text or attributes.

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