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 for behavioral disclosure. 'Delete a dashboard' implies a destructive operation but provides no information about permissions required, whether deletion is permanent or reversible, confirmation prompts, rate limits, or what happens to dependent resources. For a destructive tool with zero annotation coverage, this is dangerously 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 maximally concise with just three words. There's zero wasted language or unnecessary elaboration. It's front-loaded with the essential action and resource. For such a simple tool name, this level of brevity is appropriate rather than under-specified.

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?

This is a destructive mutation tool with no annotations, no output schema, and a minimal description. The description fails to provide critical context about permissions, irreversibility, scope, or error conditions. Given the high stakes of a delete operation and the complete lack of structured metadata, the description is woefully incomplete and inadequate for safe agent usage.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps. While it doesn't add any parameter-specific information beyond what's in the schema, the baseline for 0 parameters with full coverage is appropriately high since there's no parameter burden.

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 'Delete a dashboard' is a tautology that essentially restates the tool name 'delete_dashboard_v1'. While it confirms the action (delete) and resource (dashboard), it doesn't provide any additional specificity about scope, versioning, or what distinguishes this from other delete operations. It's minimally functional but lacks meaningful differentiation from sibling tools like 'delete_dashboard' or 'delete_dashboards'.

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 absolutely no guidance about when to use this tool versus alternatives. With multiple sibling tools like 'delete_dashboard', 'delete_dashboards', and 'delete_dashboard_v1', there's no indication of which dashboard version this targets, whether it's for single vs bulk operations, or any prerequisites. The agent receives zero contextual guidance for tool selection.

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