create_file

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

The description adds key behavioral information beyond annotations: it errors if the file already exists. Annotations already provide readOnlyHint=false and destructiveHint=true, and the description aligns with these. It does not mention other behaviors like permission requirements or return value, but the presence of an output schema and annotations reduces the burden.

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, front-loaded with the primary action, then error condition and alternative. Every word earns its place with no redundancy.

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 the tool's simplicity (2 required params, no enums, no nested objects), the description covers the essential purpose, error condition, and alternative. Annotations and output schema fill remaining gaps, making it complete.

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 coverage is 100%, so both parameters have descriptions in the input schema. The description adds no additional meaning to the parameters beyond what is already in the schema. Baseline score of 3 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?

The description clearly states the verb 'create' and resource 'file at a project-relative path', and distinguishes it from the sibling tool file_write by noting that it errors if the file already exists and to use file_write to overwrite. This provides a specific and distinguishable purpose.

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 explicitly states when to use this tool (to create a new file) and when not to (if file already exists, use file_write). This provides clear guidance on alternatives and conditions.

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