playwright_select

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Select') but doesn't explain what this entails—e.g., whether it triggers events, changes page state, requires specific permissions, or has side effects. For a tool that likely modifies page state (selecting a dropdown option), this lack of detail is a significant gap.

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, efficient sentence that directly states the tool's function. It's front-loaded with the core action and target, with no wasted words. However, the phrasing 'Select tag' could be slightly ambiguous, slightly reducing clarity.

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 no annotations and no output schema, the description is incomplete for a tool that likely performs page interactions. It doesn't cover behavioral aspects (e.g., what happens after selection), error conditions, or return values. For a 2-parameter tool in a web automation context, this leaves too many gaps for reliable use.

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 100%, with clear descriptions for both parameters (selector and value). The description adds no additional meaning beyond the schema, such as examples or constraints (e.g., selector must target a <select> element). Baseline 3 is appropriate since the schema adequately documents parameters.

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 states the action ('Select an element') and target ('on the page with Select tag'), which clarifies the tool's purpose. However, it's somewhat vague about what 'Select tag' specifically means (HTML <select> element vs. general selection), and it doesn't distinguish this from sibling tools like playwright_click or playwright_fill, which also interact with page elements.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a page loaded), exclusions, or comparisons to siblings like playwright_fill (for input fields) or playwright_click (for buttons), leaving the agent to infer usage from context alone.

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