create_project

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

With no annotations at all, the description carries the full burden, and it discloses only that a backup happens and that the file is verified. It says nothing about what the backup touches, whether existing projects are replaced, whether the call is blocking or returns a job, or what confirm/overwrite mean behaviorally — significant gaps for a mutating tool with destructive-sounding flags.

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?

A single tight sentence with the main action front-loaded and no filler. It is efficient, though the brevity is partly achieved by omitting information the agent actually needs.

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?

An output schema exists, so return values need not be explained, but for an 11-parameter mutation with no annotations the description is far too thin. Critical details — the role of confirm, what overwrite/replace_current destroy, and the relationship to the plan/job siblings — are absent.

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% across 11 parameters, so the description must compensate and largely does not. 'Back up an optional current project' only loosely gestures at backup_mode/backup_current_path, and nothing explains confirm, overwrite, replace_current, overwrite_backup, settings, template_file_path, or mesh_map_file_paths.

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 specific verbs and a resource: back up the current project, create a typed project, verify the file. An agent can tell this is the creation step rather than a status/list tool. It stops short of distinguishing itself from siblings like plan_project_creation or get_project_creation_job, which appear to belong to the same plan/execute/job family.

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?

There is no guidance on when to call this instead of plan_project_creation, get_project_creation_job, or open_project, and no stated prerequisites (for example, whether planning must happen first or whether confirm must be set). The agent must infer the workflow position from the name alone.

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