MCP Datadog 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. While 'Get' implies a read-only operation, the description doesn't specify whether this requires authentication, what permissions are needed, whether it returns a single rule or multiple rules, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, clear sentence that efficiently communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool with no parameters, and the information is front-loaded with the essential 'Get the details' action.

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 zero-parameter read tool with no output schema, the description provides the minimum viable information about what resource is being retrieved. However, it lacks context about what 'details' include, whether this retrieves a specific rule or all rules, and how to identify which rule to get. Without annotations or output schema, more behavioral context would be helpful for the agent to understand the return format.

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 lack of parameters. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. The baseline for 0 parameters with high schema coverage is 4, as the description correctly focuses on the tool's purpose rather than redundant parameter details.

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 'Get the details of a notification rule for security vulnerabilities' clearly states the verb ('Get') and resource ('notification rule for security vulnerabilities'), making the purpose understandable. However, it doesn't distinguish this tool from similar sibling tools like 'get_security_signals_notification_rule' or 'get_monitor_notification_rule', leaving ambiguity about what specifically makes this notification rule different.

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. With multiple similar 'get_notification_rule' tools in the sibling list (security_signals, monitor, security_vulnerabilities), the description fails to indicate when this specific security vulnerabilities notification rule tool is appropriate versus other notification rule types. No prerequisites, context, 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.