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 mentions 'This endpoint takes no JSON arguments,' which is useful for indicating no input parameters, but fails to disclose critical behavioral traits like whether it's a read-only operation, requires authentication, has rate limits, or what the output format might be. For a tool with zero annotation coverage, this is a significant gap.

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, front-loaded with the core purpose and followed by a clarifying detail about parameters. Every sentence earns its place with no wasted words, making it highly efficient and easy to parse.

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 complexity (a retrieval tool with no parameters), the description is incomplete. It lacks output schema, and with no annotations, it doesn't cover behavioral aspects like permissions, response format, or error handling. While concise, it fails to provide enough context for an agent to use the tool confidently beyond basic invocation.

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% description coverage, so the schema fully documents the lack of inputs. The description adds value by explicitly stating 'This endpoint takes no JSON arguments,' reinforcing the parameter semantics. With 0 parameters, the baseline is 4, and the description compensates adequately.

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 'Get a specific pipeline from your organization,' which clearly indicates a retrieval action (verb 'Get') on a resource ('pipeline') with a scope ('your organization'). It distinguishes from siblings like 'get_logs_config_pipelines' (plural) by implying retrieval of a single pipeline, though it could be more explicit about how specificity is achieved (e.g., via an identifier).

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, such as 'get_logs_config_pipelines' (likely for listing multiple pipelines) or other get-related tools. It lacks context on prerequisites, exclusions, or typical scenarios, leaving the agent to 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.