Create new project file

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses the important guarantees: file is UTF-8, project must be write-enabled, and existing files are never overwritten. It does not describe failure behavior on collision, but the no-overwrite statement is a strong safety signal.

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 tight sentences with no redundancy. The primary action is front-loaded and the critical non-overwrite behavior is stated clearly and economically.

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 simple creation tool with an output schema, this is nearly complete: it covers the precondition (write-enabled project), the encoding, and the key side effect (never overwrites). It could add what happens if the file already exists, but the essential context for safe invocation is present.

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%, and the description does not explicitly explain project, path, or content. However, the parameter names are intuitive and the phrase 'new UTF-8 file in a write-enabled project' adds useful context about what is being created. This is adequate but not exceptional.

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 ('Create') and resource ('new UTF-8 file') with a clear scope ('in a write-enabled project'). The phrase 'never overwritten' disambiguates it from modification tools like replace_text and from directory 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?

It clearly implies this is for creating new files only, and the 'write-enabled project' condition plus 'never overwritten' give the agent useful constraints. It does not explicitly name alternatives such as replace_text for existing files, but the usage context is still clear.

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