create_project

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

No annotations are provided, so the description must disclose behavioral traits itself. It states the tool creates a project and is a prerequisite, but it does not mention side effects such as whether it overwrites existing projects, what happens on duplicate names, required permissions, or the response format. This is a significant gap 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?

The description is well-structured with bold headings, bullet points, and a numbered workflow, making it easy to scan. However, there is slight redundancy: 'MANDATORY STEP 1' and 'CRITICAL: You MUST call this tool FIRST' convey the same urgency, and some phrases repeat.

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?

With no output schema and no annotations, the description should explain what the tool returns or how to interpret success, but it does not. It does provide rich workflow context and usage triggers, which helps, but it lacks details on return values, error handling, and prerequisites (e.g., whether workspace_path must exist).

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?

All five parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description does not add any parameter-specific details beyond the schema; it only mentions the tool name and general purpose.

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 uses a specific verb and resource: 'Create a new project in the memory system' and 'establishes the project in CoordMCP for tracking decisions, changes, and context.' It clearly distinguishes from sibling read tools like get_project or list_projects by emphasizing creation.

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 'WHEN TO USE' section lists concrete triggers (e.g., 'Starting ANY new project or application', 'User says Create a todo app...') and the workflow explicitly says to call this tool first. However, it does not mention when NOT to use it or alternatives, only implicit differentiation from read tools.

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