delete_households_events_notifications_by_itemRemove a specific household event notification by its unique item ID. Use this action to delete a single notification when you need to clean up or correct household alerts.
Delete One
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes | ||
| accept-language | No |
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full responsibility for behavioral disclosure. It does not mention that deletion is irreversible, whether related notifications are affected, what permissions are required, or what response to expect.
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 extremely short, but this is under-specification rather than helpful conciseness. It provides no substantive information that justifies its brevity.
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 tool with no annotations, no output schema, zero schema description coverage, and hundreds of sibling operations, this two-word description is wholly inadequate for correct selection and invocation.
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 description coverage is 0%, and the description does not explain item_id or accept-language. An agent must guess what item_id refers to and what language-related behavior the optional header controls.
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?
"Delete One" only conveys a singular delete action, which restates the verb and 'by_item' aspect of the tool name. It does not name the resource being deleted, so an agent cannot tell from the description what this tool affects.
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 indication of when to use this tool, what prerequisites exist, or how it differs from the many sibling delete tools. No alternatives or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.