testneo_run_playwright_spec_preview

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

With no annotations, the description must carry the burden. It mentions extraction and execution via Playwright SDK, but does not disclose side effects, safety, rate limits, or whether it is read-only or destructive. The behavior is only superficially described.

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 with no wasted words. However, it could be structured to front-load the core action and add details without losing conciseness. It earns points for being short but loses some for not being optimally informative.

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 output schema and 0% parameter coverage, the description is incomplete. It explains the high-level process but fails to provide enough context about inputs, outputs, and how it fits into the workflow. The tool complexity (6 params, execution endpoint) demands more detail.

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%, and the description does not explain any parameter (project_id, test_name, playwright_spec_ts, mode, confirm, idempotency_key). The agent must infer from names alone, which is insufficient for correct usage.

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 action (run a preview) and the resource (Playwright SDK spec). It distinguishes from siblings like testneo_export_playwright_spec (export) and testneo_trigger_playwright_execution (trigger different execution). However, 'preview' is not explicitly defined, leaving some ambiguity.

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. The description does not mention prerequisites, when-not-to-use, or context for choosing this tool over similar siblings like testneo_run_batch_by_tags or testneo_trigger_playwright_execution.

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