get_text

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully states that only visible text is returned and that an exception is raised if the element is not found within the default timeout. This goes beyond a bare 'Get text' statement and clarifies what the agent should expect.

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 two concise sentences with no filler. The main action and default scope are front-loaded, and the exception behavior is stated in the second sentence. Every sentence contributes useful information.

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 with one optional parameter and an output schema, the description covers the core behavior, default, and a key failure mode. Minor omissions such as selector syntax and the actual timeout duration prevent a perfect score, but the description is largely sufficient.

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%, so the description must compensate. It adds that the selector refers to an element and that omitting it targets the whole page body, which is helpful. However, it does not explain the selector syntax or matching behavior, leaving a meaningful gap for a tool with one loosely described parameter.

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 identifies the verb ('Get'), the resource ('visible text within an element'), and the default scope ('whole page body'). It distinguishes this from sibling tools like get_element_html or get_element_attribute by emphasizing visible text rather than markup or attributes.

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 gives clear context: use it to retrieve the visible text of an element, or the whole page body by default. It does not explicitly name alternatives or exclusions, but the purpose is specific enough that an agent can infer when it is appropriate.

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