playwright_text

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

No annotations are provided, so the description must bear the full burden. It discloses that only 'visible text' is returned, implying hidden elements are excluded, but it does not mention behavior for missing pages, waiting for load, or the truncation effect of the max_len parameter. The description adds limited behavioral context beyond the basic operation.

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, front-loaded sentence with no fluff or redundancy. It efficiently conveys the core purpose without wasting words.

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?

While the tool is simple and an output schema exists, the description is incomplete for correct invocation. It lacks any explanation of the max_len parameter, does not specify how the tool behaves under edge cases (e.g., no page open), and provides no guidance on session prerequisites. These gaps make it insufficient for an agent to fully understand the tool's behavior.

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 has one parameter (max_len) with 0% coverage from the description, and the description does not mention the parameter at all. Since schema coverage is low, the description needed to compensate by explaining what max_len controls (e.g., character limit, truncation behavior), but it fails to do so.

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 tool's function with a specific verb ('Return') and resource ('visible text of the current page'). It also distinguishes itself from siblings like playwright_html (which returns HTML) and playwright_screenshot (which captures an image).

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 by referencing the 'interactive session' and 'current page,' but it does not explicitly state when to use this tool over alternatives like playwright_html. There is no mention of when not to use it or any prerequisites.

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