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 of behavioral disclosure. It states the tool deletes a rule, implying a destructive operation, but doesn't mention critical details like required permissions, whether the deletion is permanent or reversible, or any rate limits. The note about site unavailability adds some context, but overall, the description lacks sufficient behavioral transparency 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 highly concise and well-structured, consisting of two sentences: one stating the purpose and another providing a critical note. Every sentence adds value without redundancy, making it efficient and front-loaded with essential information.

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's complexity (a deletion operation with no parameters), the description is partially complete. It covers the purpose and a site restriction but lacks details on behavioral aspects (e.g., permissions, reversibility) and output (no output schema is provided). For a destructive tool with no annotations, this leaves gaps in understanding the full context of use.

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 (schema description coverage is 100%), so there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides, earning a baseline score of 4 for this dimension, as it doesn't introduce confusion or omissions regarding parameters.

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 tool's purpose: 'Delete a specific Workload Protection agent rule.' It includes a specific verb ('Delete') and resource ('Workload Protection agent rule'), making the action unambiguous. However, it doesn't distinguish itself from sibling tools like 'delete_security_monitoring_cloud_workload_security_agent_rule', which appears to serve a similar function, reducing the score from a perfect 5.

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 some usage guidance by noting the tool is unavailable for the Government (US1-FED) site, which is helpful context. However, it doesn't specify when to use this tool versus alternatives (e.g., other deletion tools in the sibling list) or any prerequisites for invocation. The guidance is implied but incomplete.

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