delete_file_or_folder

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

With no annotations provided, the description carries full burden. It notes the operation is permanent ('kalıcı olarak siler') and requires confirmation for deletion and recursion for non-empty folders. This adequately discloses key behaviors without contradiction.

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?

Two sentences, minimal waste, front-loaded purpose. Every sentence serves a clear function: stating what the tool does and giving essential usage requirements.

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 presence of an output schema and 3 parameters, the description covers the core purpose and key parameter conditions. It does not describe output behavior or error handling, but the output schema can address that. For a simple delete tool, this is adequate.

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 schema coverage is 0%, so the description must compensate. It adds meaning for confirm (required for deletion) and recursive (required for non-empty folders), but provides no description for the path parameter, which is required. Partial coverage merits a 3.

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 clearly states 'Dosya veya klasörü kalıcı olarak siler' (permanently deletes file or folder), specifying the action and resource. It unambiguously distinguishes deletion from sibling tools like rename, move, or copy.

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 explicit conditions for using the confirm and recursive parameters: 'Silme işlemi için confirm=true gerekir' and 'Dolu klasörlerde recursive=true gerekir'. While it does not explicitly mention when not to use the tool, the guidance is clear enough for correct invocation.

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