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. It discloses behavioral traits like site restrictions (Government-only) and error responses (403, 429), but lacks details on rate limits, authentication needs, pagination, or data format beyond examples. This partial disclosure is adequate but incomplete for a tool with no annotations.

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 overly verbose, including extensive HTTP response details (status codes, content types, examples) that are redundant with an output schema. This clutters the core purpose and usage note, making it less front-loaded and efficient. Sentences like 'Responses:' and example JSON do not earn their place in a tool description.

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 an output schema and 0 parameters, the description is somewhat complete with purpose and usage constraints. However, it lacks context on what 'agent rules' entail, behavioral details like rate limits, and does not fully compensate for missing annotations, leaving gaps in understanding the tool's operation.

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 does not add parameter details, which is appropriate, but it could have mentioned optional query parameters if any existed. Baseline is 4 due to no 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 states the tool 'Get the list of agent rules,' which clearly indicates its purpose as a read operation. However, it lacks specificity about what 'agent rules' are (e.g., security rules, configuration rules) and does not differentiate from sibling tools like 'GetCloudWorkloadSecurityAgentRule' (singular) or 'ListSecurityMonitoringRules,' making it vague in context.

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 explicit context with a note: 'This endpoint should only be used for the Government (US1-FED) site,' which clearly indicates when to use it. However, it does not mention when not to use it or suggest alternatives for non-government sites, leaving some guidance gaps.

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