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

Without annotations, the description carries full burden for behavioral disclosure. It mentions 'ephemeral' and '$0.02/call,' which add some context, but it does not explain failure behavior, side effects, authentication requirements, or what AEP-1.0 evidence actually contains. The lack of an output schema makes this gap significant for a browser automation tool.

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, compact sentence that includes the core behavior, cost, and evidence format. Every phrase contributes meaning, with no filler or redundancy.

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?

This tool has nested parameters, no annotations, and no output schema, yet the description is extremely short. It omits critical details like how the action object should be structured, what AEP-1.0 evidence includes, and how results are returned, making it incomplete for a tool of this complexity.

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 for all parameters. It only partially explains 'expected' via 'selector or text assertion.' The action object's types (click/type/goto), the purpose of url, and the role of request_id are entirely unexplained, leaving agents without the needed semantics for invocation.

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 specifies a clear action: 'Run one ephemeral Playwright browser action and verify a selector or text assertion, returning AEP-1.0 evidence.' This identifies the resource (browser action), the operation (verify), and the output (evidence), effectively differentiating it from siblings like web_extract or batch_url_json.

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 provides no explicit guidance on when to use this tool versus alternatives like web_extract or purchase_web_extraction_sample. It implies usage through its description but lacks any when/when-not context or alternative recommendations.

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