create_corrupted_file_tool

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

With no annotations provided, the description carries the full burden and does add value by asserting 'Never modifies the original' and illustrating corruption types. However, it omits details such as file naming, output location, permissions, or any side effects beyond creating the corrupted copy.

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 compact and front-loaded, with the most important guarantee stated first. The example list is useful but could be clearer (e.g., 'corrupted JPEG' is vague, and there's minor formatting corruption), though it does not waste words.

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?

The tool has eight parameters, no required fields, no enums, and an output schema, but the description leaves parameter semantics entirely unexplained. While the output schema may cover return values, the description inadequately addresses the complexity of configuring corruption, making it incomplete for a tool of this scope.

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, but it does not explain any of the eight parameters. The examples loosely relate to file_type and corruption types, but the user receives no guidance on how to set seed, severity, overwrite, or output_directory.

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+resource construction ('Create a corrupted copy of a file') and clearly states the tool's purpose of testing error handling. It differentiates from sibling tools by emphasizing the corrupted-copy behavior and explicitly guarantees the original file is never modified.

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 phrase 'for testing error handling' implies the recommended use case, and the examples suggest scenarios involving file types and corruption. However, it does not explicitly enumerate when to use this tool versus siblings like create_dummy_file_tool, nor does it state exclusions.

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