testneo_create_web_project

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

No annotations are provided, so the description fully bears the burden. It discloses write guard, default environment creation, and Lighthouse performance audits, providing good behavioral context for a mutation 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?

Four sentences packed with essential information: purpose, API mapping, guard, default behavior, and audit setting. No redundancy, well front-loaded.

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?

No output schema is provided, and the description does not mention return values. While key behavioral aspects are covered, details about parameters like environment, status, and idempotency_key are missing, leaving some gaps for a complex 12-parameter tool.

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 coverage is low (17%), but the description provides meaning for key parameters (base_url, credentials, create_default_environment, project_settings) beyond the schema. Not all 12 parameters are covered, but enough value is added.

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 'Create a new web automation project' and mentions it mirrors POST /api/web/v1/projects, providing a specific verb and resource. It differentiates from siblings like testneo_create_web_project_environment.

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 mentions guarded conditions (TESTNEO_MCP_ALLOW_WRITE=true, confirm=true) and explains default vs. project-only creation via create_default_environment. However, it does not explicitly state when to use this tool over alternatives.

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