Delete Instruction

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

Annotations already indicate this tool is not read-only and not idempotent, which is consistent with deletion. The description adds the file type and directory location, but does not disclose critical behavioral details like whether deletion is permanent, if confirmation is needed, or error handling for missing files. With annotations covering the safety profile, the minimal addition is acceptable but not exceptional.

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, clear sentence with no wasted words. It fits on one line and immediately conveys the tool's core action and resource.

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 output schema exists, the description doesn't need to detail return values. However, it omits practical details like what happens on success, failure cases (e.g., file not found), and whether the operation is reversible. For a deletion tool of this nature, the description is adequate but leaves common questions unanswered.

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?

Input schema coverage is 100%, so the schema already documents the single parameter 'instruction_name' with the description 'with or without extension'. The tool description does not elaborate further on parameter meaning, formatting, or valid values, offering no added value beyond the schema.

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 precisely states the action ('Delete') and the resource ('a VS Code .instructions.md file from the prompts directory'), making the tool's purpose unmistakable. It clearly distinguishes itself from sibling tools like create_instruction, get_instruction, update_instruction, and list_instructions by specifying the delete 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?

The description offers no guidance on when to use this tool versus alternatives, such as when to delete vs. update or list instructions. No contextual cues or exclusions are provided, leaving an AI agent without decision-making support for tool selection.

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