MCP Datadog Server

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

With no annotations provided, the description carries full burden but offers no behavioral information. It doesn't mention whether deletion is permanent, requires specific permissions, has side effects on related configurations, or provides any confirmation. For a destructive operation 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 extremely concise at just three words. While under-specified, it's not verbose or poorly structured. Every word serves a purpose (verb + object), making it efficiently front-loaded despite its inadequacy.

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 tool with no annotations, no output schema, and critical security implications (sensitive data scanner), the description is completely inadequate. It doesn't explain what happens after deletion, whether there's confirmation, what 'rule' refers to, or any safety considerations. The context demands much more information.

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% coverage, so the schema fully documents the absence of parameters. The description doesn't need to add parameter information, and it doesn't contradict the schema. The baseline for 0 parameters is 4, as the description doesn't mislead about parameters.

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 given rule' restates the tool name without adding specificity. It doesn't clarify what type of rule (sensitive data scanner configuration rule) or what 'given' means in practice. While it includes the verb 'delete', it lacks differentiation from sibling delete tools like delete_sensitive_data_scanner_config_group.

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's no mention of prerequisites, dependencies, or when deletion is appropriate versus updating or creating rules. Given the sensitive nature implied by 'sensitive_data_scanner', this is a significant omission.

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