ecp_files_add_file

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

No annotations are provided, so the description carries the full burden. It states the tool creates an empty file, which implies a write operation, but doesn't disclose whether it overwrites existing files, what happens if the destination doesn't exist, whether parent directories are created, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence with no waste. It's front-loaded with the core action. However, it's so brief that it sacrifices valuable context that could be added without much length.

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 2-parameter mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain path semantics, overwrite behavior, or return values. The sibling list shows many file operations, but this description doesn't help the agent understand how this tool fits into the file management workflow.

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%, so the description must compensate. It doesn't explain what 'destination' means (full path? directory?) or what 'file_name' should look like (extension? format?). The description adds no meaning beyond the parameter names themselves, leaving the agent to guess the semantics of both required parameters.

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 'Create a new empty file.' clearly states the verb (create) and resource (a new empty file). It distinguishes from siblings like ecp_files_add_folder (folder vs file) and ecp_files_write (which writes content vs creating empty). However, it doesn't explicitly mention the destination path or file_name parameters, which are the core of the operation.

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?

No guidance on when to use this tool vs alternatives. It doesn't mention that ecp_files_write might be better for creating a file with content, or that ecp_files_add_folder is for directories. The context of 'empty file' is implied but no explicit when/when-not guidance is given.

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