Create a new project file

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

The description discloses the key behavioral trait of refusing to overwrite existing paths. Annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) are consistent, but the description adds useful context beyond their boolean values.

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 sentence that is concise and front-loaded. Every word is necessary, no fluff.

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?

Given 4 parameters, no output schema, and many sibling tools, the description is too sparse. It omits details on content defaults, createParents behavior, return values, and when to choose this over other file manipulation tools.

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 description does not describe any parameter details. Only 25% of parameters have schema descriptions (project has a description). The text adds no meaning about path, content, or createParents, failing to compensate for low schema coverage.

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 tool 'Creates a new file and refuses to overwrite an existing path.' This distinguishes it from sibling tools like write_file, which likely overwrites. The verb 'creates' and resource 'new file' are specific.

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 implicitly suggests use when creating a new file and wanting to avoid overwriting, but does not explicitly provide when-to-use or when-not-to-use guidance, nor mention alternatives beyond the overwrite refusal.

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