delete_functionDelete a Firecracker Function by ID, removing its public webhook endpoint when enabled. Use it to clean up unused functions and their exposed endpoints.
Delete a Firecracker Function, including its public webhook endpoint when enabled.
| Name | Required | Description | Default |
|---|---|---|---|
| function_id | Yes | Function ID from list_functions |
Changes observed during successful MCP inspections.
v2.3.16Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the operation as destructive, open-world, and not read-only. The description adds useful behavioral context beyond annotations by noting that the public webhook endpoint is also deleted when enabled. It does not cover authorization requirements or explicitly state irreversibility, so it does not reach 5.
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, front-loaded sentence with no wasted wording. It communicates the main action and the notable cascade effect immediately.
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 simple one-parameter delete tool with complete schema coverage and annotations carrying the destructive safety profile, the description is nearly complete. It adds the important webhook-endpoint cascade detail, though it omits prerequisites and explicit irreversibility.
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 has 100% description coverage and documents function_id as coming from list_functions. The description adds no parameter meaning beyond the schema, so 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 states a specific verb and resource: "Delete a Firecracker Function," and adds the cascade behavior for its public webhook endpoint. This clearly distinguishes it from sibling tools such as delete_firecracker_snapshot, delete_temp_vm, and delete_snapshot.
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 gives no guidance about when to use this tool versus alternatives, no prerequisites, and no when-not-to-use conditions. It only implies usage through the verb "Delete."
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.