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 adds value by specifying the endpoint's restriction to the Government site and detailing HTTP responses (200, 403, 404, 429) with examples, which helps understand error handling and success conditions. However, it lacks details on permissions, rate limits, or data format beyond the basic examples, leaving some behavioral aspects unclear.

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 and poorly structured, including extensive HTTP response details (e.g., status codes, content types, examples) that might be redundant if an output schema exists. It front-loads the purpose but buries it in unnecessary technical documentation, making it less efficient and harder to parse quickly. Sentences like the response examples do not earn their place in a concise 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 context: 1 parameter with 100% schema coverage, an output schema exists (implied by the response details), and no annotations, the description is fairly complete. It covers the purpose, a key restriction (Government site), parameter info, and response behaviors. However, the inclusion of verbose HTTP details may be excessive, and it could benefit from more guidance on sibling differentiation or operational constraints.

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 schema description coverage is 100%, with the parameter 'agent_rule_id' fully documented in the input schema. The description repeats this parameter info in a 'Path Parameters' section but does not add significant meaning beyond what the schema provides (e.g., format, examples, or constraints). This meets the baseline for high schema coverage but offers no extra insights.

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 details of a specific agent rule.' This is a specific verb ('Get') and resource ('agent rule'), making the function unambiguous. However, it does not explicitly differentiate from sibling tools like 'ListCloudWorkloadSecurityAgentRules' or other 'Get' tools, which slightly limits its clarity in a crowded 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 some usage guidance with a note: 'This endpoint should only be used for the Government (US1-FED) site.' This implies a specific context or restriction. However, it does not offer explicit alternatives (e.g., when to use this vs. 'ListCloudWorkloadSecurityAgentRules') or broader when/when-not guidance, leaving usage somewhat implied rather than fully articulated.

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