dietbox_patient_delete
Permanently delete a patient from Dietbox. Irreversible.
Bulk support: accepts patient_ids for batched execution.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| patient_id | Yes | ||
| patient_ids | No |
Permanently delete a patient from Dietbox. Irreversible.
Bulk support: accepts patient_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| patient_id | Yes | ||
| patient_ids | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description reinforces annotations (destructiveHint=true) by stating 'Permanently delete' and 'Irreversible'. Additionally, it adds behavioral context beyond annotations by mentioning bulk support via patient_ids.
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: first states purpose and irreversibility, second adds bulk feature. Extremely concise and front-loaded with critical information.
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?
Covers core operation, irreversibility, and bulk support. Lacks explanation of the 'account' parameter and return value, but 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?
Schema has 0% description coverage. The description explains patient_ids for batch execution, adding meaning beyond the schema. However, it does not describe the 'account' parameter, leaving its purpose unclear.
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?
Description clearly states 'Permanently delete a patient from Dietbox' with a specific verb and resource. Distinguishes from sibling tools by focusing on deletion, while other patient tools handle get, list, create, and update.
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?
Indicates irreversible action ('Irreversible') and mentions bulk support for batched execution, providing context for use. However, it does not explicitly state when not to use this tool or mention alternatives like update for reversible changes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.