MCP Datadog Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a destructive operation (implied by 'delete' but not explicit), what permissions are required, whether deletion is permanent or reversible, what happens to associated data, or what the response looks like. For a deletion tool with zero annotation coverage, this is critically 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 extremely concise ('Delete a monitor') but this brevity represents under-specification rather than efficient communication. While it's front-loaded with the core action, it lacks necessary context that would make it genuinely helpful. The single sentence doesn't earn its place by providing value beyond the tool name.

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 deletion tool with no annotations, no output schema, and no parameter documentation needed, the description is completely inadequate. It doesn't address critical questions about what gets deleted, confirmation requirements, error conditions, or system behavior. The agent cannot safely invoke this tool based on the provided description alone.

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 fully documents the lack of parameters. The description doesn't need to add parameter information, and it doesn't incorrectly suggest parameters exist. The baseline for 0 parameters with complete schema coverage is 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 'Delete a monitor' is a tautology that essentially restates the tool name 'delete_monitor_v1'. While it indicates the action (delete) and resource (monitor), it lacks specificity about what a 'monitor' is in this context and doesn't differentiate from sibling tools like 'delete_monitor' (without the _v1 suffix).

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. There are multiple sibling deletion tools (delete_monitor, delete_monitor_v1, delete_monitor_notification_rule, delete_monitor_policy) with no indication of when this specific version should be used. No prerequisites, conditions, or exclusions are mentioned.

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