Create a new empty page object for Easy Spec Playwright projects by providing its name, folder, and project path.
Create a new, empty page object.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| folder | No | ||
| project | No | Path to the project root (same folder the side panel connects to). Defaults to the EASYSPEC_PROJECT environment variable if omitted. |
Changes observed during successful MCP inspections.
v1.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a write operation but does not disclose side effects, such as whether existing page objects are overwritten, whether directories are created, or what the response contains. With no annotations (e.g., destructiveHint), the agent cannot infer safety or failure behavior.
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 concise sentence that immediately communicates the core action and object. No unnecessary words or filler.
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?
The description lacks essential context for correct invocation: no mention of return format, error conditions, interaction with 'folder' and 'project' defaults, or relationship to project structure. Given the sparse schema and no annotations, this is a notable gap.
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?
Only 'name' is required and self-explanatory; 'folder' and 'project' have no schema descriptions. The 'project' description clarifies its default, but 'folder' semantics remain unclear, so parameter meaning is only partially covered beyond the schema.
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 ('create') and the resource ('a new, empty page object'), making the tool's purpose unambiguous. It is distinct from related sibling tools like create_flow or create_scenario.
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 or prerequisites. It does not mention whether a project context is required, how 'folder' is resolved, or any conditions that would make this tool inappropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.