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. It states the tool takes no JSON arguments, which is useful, but lacks critical behavioral details: whether this is a read-only operation, if it requires specific permissions, what the return format looks like (list, paginated, etc.), or any rate limits. For a tool with zero annotation coverage, this is insufficient.

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 two sentences with zero waste. The first sentence states the purpose, and the second clarifies the parameter situation. It's front-loaded and appropriately sized for a simple tool with no parameters.

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's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and parameter situation but lacks behavioral context (e.g., read-only nature, return format). For a tool with no structured fields to rely on, it should do more to compensate, but it meets the bare minimum.

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 description explicitly states 'This endpoint takes no JSON arguments,' which aligns with the input schema (0 parameters, 100% coverage). Since there are no parameters, the description effectively covers the parameter semantics by confirming the absence of inputs, warranting a score above the baseline of 3 for high schema coverage.

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 action ('Get all pipelines') and resource ('from your organization'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'get_logs_config_pipeline' (singular) or 'create_logs_config_pipelines', but the scope is clear. It's not a tautology as it adds meaningful context beyond the tool name.

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 'get_logs_config_pipeline' (singular) or 'create_logs_config_pipelines', nor does it specify prerequisites, filtering options, or typical use cases. The agent must infer usage from the name alone.

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