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. 'Delete' implies a destructive mutation, but the description doesn't mention whether this operation is reversible, what permissions are required, what happens to associated rules or data, or any rate limits. For a destructive operation with zero annotation coverage, this represents a significant gap in behavioral 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 extremely concise ('Delete a given group') but this brevity comes at the cost of under-specification. While it's front-loaded and wastes no words, it fails to provide essential context that would help an agent understand and use the tool effectively. The single sentence doesn't earn its place by adding sufficient value.

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 minimal description, this is incomplete. The description doesn't explain what constitutes 'a given group', how groups are identified, what the deletion consequences are, or what (if anything) is returned. Given the tool's destructive nature and the rich sibling tool ecosystem, more context is needed for safe and effective use.

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 zero parameters (schema coverage 100%), so there are no parameters to document. The description doesn't need to compensate for any parameter documentation gaps. A baseline score of 4 is appropriate since the schema fully describes the empty parameter set, and the description doesn't need to add parameter semantics.

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 group' is a tautology that essentially restates the tool name 'delete_sensitive_data_scanner_config_group'. It specifies the verb 'delete' and resource 'group', but lacks specificity about what type of group (sensitive data scanner configuration group) and provides no differentiation from sibling tools like 'delete_sensitive_data_scanner_config_rule' or 'update_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 absolutely no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, conditions for use, or comparison to sibling tools like 'update_sensitive_data_scanner_config_group' or 'create_sensitive_data_scanner_config_groups'. The agent receives no contextual usage information.

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