MCP Datadog Server

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

No annotations are provided, so the description carries full burden. While 'Delete' implies a destructive mutation, the description doesn't disclose critical behavioral traits: whether deletion is permanent/reversible, required permissions, confirmation prompts, error conditions, or side effects. For a destructive operation with zero annotation coverage, this minimal disclosure is inadequate.

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 front-loads the core action ('Delete a Datadog-AWS integration') and adds necessary specificity. There's zero wasted verbiage, and every word earns its place by clarifying what gets deleted and how it's identified.

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 deletion tool with no annotations, no output schema, and 0 parameters, the description is incomplete. It lacks critical context about the mutation's consequences, success/failure responses, authentication requirements, or error handling. The agent cannot safely invoke this tool without guessing about its behavior and outcomes.

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 (100% coverage with empty properties), so no parameter documentation is needed. The description mentions `account_id` and `role_name parameters` but these appear to be informational rather than actual schema parameters. Since there are no parameters to document, the description doesn't need to compensate, earning a baseline 4.

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 specific action ('Delete') and target resource ('a Datadog-AWS integration'), with precise matching criteria ('matching the specified `account_id` and `role_name parameters`'). It distinguishes from sibling tools like 'create_integration_aws' and other delete operations by specifying the exact resource type and parameters.

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, prerequisites, or exclusions. It mentions parameters but doesn't explain when deletion is appropriate or what happens after deletion. Given the destructive nature implied by 'Delete', this lack of usage context is a significant gap.

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