delete_lines_code

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the operation without detailing consequences like irreversibility, error handling for out-of-range line numbers, or whether the file is modified in place. This is a significant gap for a mutation tool.

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, focused sentence with no filler. It is front-loaded and efficiently communicates the core operation, though it lacks supplementary guidance that would be covered elsewhere.

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 absence of annotations and output schema, the description is sparse. It confirms the operation but omits important contextual details such as prerequisites, edge cases (e.g., startLine > endLine), and behavioral expectations. For a mutation tool, this is incomplete but still minimally functional due to the clear schema.

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?

The input schema already documents all three parameters (path, startLine, endLine) with clear descriptions, including 1-based inclusive line numbering. The description 'Delete specific lines' adds no additional semantic value beyond what the schema provides, but with 100% schema coverage, the baseline 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 'Delete specific lines from a file' uses a specific verb (delete) and identifies the exact resource (specific lines in a file). It clearly distinguishes from siblings like delete_file_code (whole file) and replace_lines_code (line replacement), making the tool's purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as delete_file_code for removing entire files or replace_lines_code for modifying line content. No context, exclusions, or alternative references are given.

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