create_households_events_notificationsCreate a household event notification to trigger alerts, specifying a name and optional Apprise URL and accepted language.
Create One
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| appriseUrl | No | ||
| accept-language | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 the full burden of behavioral disclosure, but 'Create One' only restates the create action. It does not mention that a notification record is created, whether permissions are required, what side effects occur, or what happens on success or failure.
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 effective conciseness. It provides no front-loaded context or useful information, so the brevity does not help an agent.
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 create operation with three parameters and no annotations, this description is severely incomplete. The presence of an output schema does not compensate for the absence of purpose, parameter meaning, usage guidance, or behavioral expectations.
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 adds no meaning to the three parameters. Even the required 'name' parameter is not explained, and the optional appriseUrl and accept-language parameters receive no semantic context whatsoever.
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 'Create One' is tautological with the tool name and does not specify what resource is created, what the action does, or how it differs from sibling tools like get/update/delete/list or the by_item_test variant. An agent cannot determine what 'One' refers to from the description alone.
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?
There is no guidance on when to use this tool versus alternatives. The sibling list contains many related notification endpoints, but the description gives no criteria, exclusions, or selection hints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.