Disable alert trigger

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

Annotations already declare that this is destructive, idempotent, non-read-only, and operates in an open-world context. The description adds no behavioral context beyond restating the action, such as whether disabling is reversible or what happens to the alert/trigger state.

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 a single front-loaded sentence with no filler. Its brevity is appropriate structurally, even though it leaves semantic gaps elsewhere.

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 destructive mutation tool with two required parameters at 0% schema description coverage and no output schema, the description is too sparse. Annotations cover safety traits, but the agent still lacks parameter guidance and usage context.

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 either required parameter. The words 'alert' and 'trigger' loosely map to `id` and `trigger`, but the description gives no format, source, or expected value guidance.

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 states a specific verb and resource: disabling a trigger on an alert. It is clear enough to distinguish this from the sibling `shodan_alert_enable_trigger`, although it does not explicitly name the alternative.

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, when not to use it, or which sibling to choose instead. The only implied usage is the obvious inverse of the tool name.

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