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. While 'Delete' implies a destructive mutation, the description doesn't state whether this action is reversible, what permissions are required, whether it affects associated dashboards, or what the response looks like (success/failure indicators). For a destructive operation with zero annotation coverage, this is a significant gap in transparency.

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. It's front-loaded with the key verb and resource, with zero wasted words. For a simple deletion tool with no parameters, this level of conciseness is appropriate and effective.

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 that this is a destructive mutation tool with no annotations, no output schema, and 0 parameters, the description is incomplete. It doesn't address critical context such as how the target is specified, what happens to contained dashboards, whether confirmation is needed, or what the return value indicates. The agent lacks sufficient information to use this tool safely and effectively.

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, so there are no parameters to document. The description doesn't need to compensate for any parameter gaps, and it correctly implies a singular deletion action without specifying parameters. However, it doesn't clarify how the dashboard list is identified (e.g., by ID, name, or context), which might be assumed but isn't explicit.

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 verb ('Delete') and resource ('a dashboard list'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'delete_dashboard' or 'delete_dashboard_public' by specifying 'dashboard list' rather than other dashboard-related resources. However, it doesn't specify whether this is a manual deletion process versus automated, which could be inferred from the tool name but isn't explicit in the description.

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 to identify which dashboard list to delete), consequences of deletion, or when to choose this over other deletion tools like 'delete_dashboard_lists_manual_dashboards'. The agent must infer usage from the name alone, which is insufficient for proper tool selection.

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