project_new

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

Even with no annotations, the description discloses an important behavioral quirk: calling it while a project is open would open a separate application window. It also clarifies that it does not replace the current project in-place. This gives agents critical expectations beyond the simple 'create' verb.

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?

Two sentences with no filler. The main purpose is stated first, followed immediately by the necessary precondition and instruction sequence. Every clause adds useful information for correct invocation.

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?

For a zero-parameter creation tool with no output schema, the description is sufficient: it gives the action, the precondition, the fallback when the precondition is unmet, and the relevant sibling tools to use first. Nothing critical is missing.

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?

The tool has zero parameters and an empty schema, so there is no parameter detail to add. The baseline of 4 applies, and the description's note about saving/closeing relates to preconditions rather than parameters, which is appropriate.

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?

States a precise action: 'Create a new project in the current window.' It clearly distinguishes itself from project_open, project_close, and project_save_as by emphasizing the current-window behavior and the prerequisite that no project is open.

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?

Explicitly tells the agent when the tool works: only when no project is currently open. It also gives the correct alternative sequence—project_save_as if needed, then project_close—and explains the consequence of ignoring the precondition.

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