MCP Datadog Server

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

No annotations are provided, so the description carries the full burden. It states the tool performs a deletion, implying it's destructive, but doesn't disclose critical behavioral traits such as whether deletion is permanent, requires specific permissions, has side effects (e.g., stopping notifications), or returns confirmation details. This leaves significant gaps for a mutation tool.

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, efficient sentence that directly states the tool's purpose without any fluff. It's front-loaded and wastes no words, making it easy to parse quickly.

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?

Given the tool is a deletion operation (implied mutation) with no annotations and no output schema, the description is incomplete. It lacks information on behavioral aspects like permanence, permissions, or response format, which are crucial for safe and correct usage. The zero-parameter schema doesn't mitigate this gap for a destructive action.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are defined or required. The description doesn't add parameter details, which is appropriate since there are none to document. A baseline of 4 is justified as the description doesn't need to compensate for missing parameter information.

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 notification rule for security vulnerabilities'), which is specific and unambiguous. However, it doesn't distinguish this tool from other 'delete_*' siblings in the list, such as 'delete_security_signals_notification_rule' or 'delete_monitor_notification_rule', which target different notification rule types.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing the rule ID), when-not-to-use scenarios (e.g., if the rule is active), or direct alternatives like 'update_security_vulnerabilities_notification_rule' for modification instead of deletion.

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