mudbase_delete_filePermanently delete a file from a Mudbase storage bucket by providing project, bucket, and file IDs. Irreversible removal of stored files.
Permanently delete a file from a Mudbase storage bucket. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| fileId | Yes | The file ID within the bucket. | |
| bucketId | Yes | The storage bucket ID within the project. | |
| projectId | Yes | The Mudbase project ID. |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations mark destructiveHint, and the description goes beyond that by explicitly warning that deletion is permanent and cannot be undone. This is useful behavioral disclosure for an irreversible action.
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 short sentences carry the essential information: the action, the target, and the irreversibility. No filler or redundancy.
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 delete operation, the description covers what it does and its permanence. It doesn't explain return values or behavior on nonexistent files, but the three required parameters are all documented and no output schema exists. Minor omission, not a blocker.
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 required parameters with descriptions and 100% coveragecyst. The description adds no parameter-specific detail beyond what the schema provides, so it meets but does not exceed the baseline.
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 ('delete') and identifies the exact resource ('a Mudbase storage bucket' file), making the tool's purpose immediately clear and distinguishing it from document-level operations.
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 action and resource are clear, so when to use it is implied proportional to file deletion. However, it does not explicitly state when not to use it or how it differs from sibling tools like deleting a document.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.