shodan_alert_remove_notifierRemoves a notifier from a Shodan alert by alert ID and notifier ID, so you can stop that alert from sending notifications through the specified channel.
Remove a notifier from an alert.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| notifier_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, and the description is consistent with them. However it adds nothing beyond them — critically, it does not clarify whether detaching also deletes the notifier object itself or how existing trigger behavior is affected.
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?
A single efficient sentence with no waste, but it is terse to the point of under-specification for a destructive two-parameter mutation.
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?
A destructive, open-world mutation with no output schema and zero parameter descriptions needs more than one sentence; the agent lacks ID semantics, side effects, and confirmation of what the response contains.
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%, so both 'id' and 'notifier_id' are undocumented strings. The description's vocabulary ('alert', 'notifier') hints at the mapping but never states which ID is the alert and which is the notifier, leaving real ambiguity for two required params.
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?
Specific verb 'Remove' plus resource 'notifier from an alert' states the operation and scope clearly. It distinguishes itself implicitly from shodan_alert_add_notifier, though the inverse pairing is left for the agent to infer.
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?
No guidance on when to detach a notifier versus deleting it or using shodan_notifier_delete, and no prerequisites or alternatives named. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.