create_file

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

The description discloses mutation (create file), rejection on existing file, and dry_run default, adding value beyond the readOnlyHint=false annotation which only indicates write. The description provides full behavioral context.

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 extremely concise with three short sentences, front-loading the purpose and key behavior. Every sentence adds value 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?

For a mutation tool with 7 parameters (all documented in schema) and no output schema, the description covers essential behavioral aspects (create, reject, dry_run). No gaps.

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 the schema already describes parameters. However, the description adds meaning by emphasizing the dry_run default and the rejection behavior, which are critical for agent decision-making.

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?

Description clearly states the action 'Create a new file', the resource 'repository', and a key behavioral constraint 'Rejects if the file already exists', distinguishing it from siblings like update_file or delete_file.

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 and schema clarify the dry_run default and its conditional use (set to false only after user confirmation). While not explicitly stating when to use vs alternatives, the rejection behavior implies it's for new files only, providing sufficient guidance.

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