shodan_alert_delete

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds no context beyond the annotations. While destructiveHint=true indicates the destructive nature, the description doesn't mention permanence, reversibility, or any side effects, which would be valuable for a delete operation.

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 concise, consisting of a single clear sentence. It is front-loaded and to the point, but it omits any helpful context, making it slightly too sparse for a destructive tool.

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 simple destructive tool with one parameter and no output schema, the description should at least note that the deletion is permanent or irreversible. The current text is functional but incomplete given the destructiveHint.

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 schema already provides 100% coverage for the only parameter (alert_id). The description adds no additional detail about the parameter, so the baseline of 3 is appropriate.

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 clearly states the action ('Delete') and the resource ('a network alert'). It is unambiguous and distinguishes itself from sibling alert tools by the action, though it doesn't explicitly mention the ID parameter.

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 is given on when to use this tool versus alternatives like shodan_alert_create or shodan_alert_get. The context implies it's for removing alerts, but there are no explicit conditions, prerequisites, or warnings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.