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 performs a deletion, implying a destructive mutation, but does not address critical aspects like required permissions, confirmation prompts, reversibility, rate limits, or error handling. This is a significant gap for a mutation tool with zero annotation coverage.

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 action and target without any fluff or redundancy. It is front-loaded and wastes no words, making it highly concise and well-structured for quick understanding.

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 with no annotations, no output schema, and zero parameters, the description is incomplete. It fails to cover behavioral aspects like safety warnings, confirmation needs, or response format, which are crucial for a destructive tool. The simplicity of the schema does not compensate for these missing contextual details.

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% description coverage, meaning no parameters are documented in the schema. The description does not mention any parameters, which is appropriate here as the tool likely operates on a pre-configured integration. With zero parameters, the baseline is 4, and the description does not contradict or add unnecessary detail.

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 given Datadog-Azure integration from your Datadog account'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'delete_integration_aws' or 'delete_integration_gcp_account', which have similar naming patterns but target different integrations, so it misses full sibling distinction.

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, such as other delete_integration_* tools for different cloud providers or non-deletion options. It lacks context on prerequisites, conditions, or exclusions, leaving the agent without usage direction beyond the basic action.

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