Datadog MCP 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. It only describes the tool as a 'Get' operation, implying it's read-only, but doesn't specify permissions needed, rate limits, pagination, or what 'all suppression rules' entails (e.g., scope, filters). The HTTP response examples add some error handling context (403, 429), but this is minimal for a tool with no annotation support.

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 front-loaded with the core purpose ('Get the list of all suppression rules.'), but it's bloated with extensive HTTP response documentation (200, 403, 429 examples) that repeats what an output schema could cover. This adds unnecessary length without providing additional value for tool selection, reducing conciseness.

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 the tool has 0 parameters (schema coverage 100%) and an output schema exists (implied by context signals), the description doesn't need to detail inputs or return values. However, it lacks context about behavioral aspects like permissions or scoping, and the HTTP response details are redundant with output schema. It's minimally complete but could better address usage and transparency gaps.

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 no parameter documentation is needed. The description doesn't add any parameter details, which is appropriate here. A baseline of 4 is given since the schema fully handles the parameter semantics, and the description doesn't need to compensate.

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 tool's purpose: 'Get the list of all suppression rules.' This is a specific verb ('Get') and resource ('suppression rules'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'GetSecurityMonitoringSuppression' (singular vs. plural), which could cause confusion about when to use each.

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 sibling tools like 'GetSecurityMonitoringSuppression' (which retrieves a single rule) or 'ListSecurityMonitoringRules' (which might list different types of rules), leaving the agent to infer usage from names alone. There's no context about prerequisites, scoping, or exclusions.

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