MCP Datadog Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It clearly states this is an update operation (implying mutation) and importantly adds the critical behavioral detail: 'Using this method updates your pipeline configuration by **replacing** your current configuration with the new one.' This warns about destructive replacement behavior, which is valuable context beyond just 'update'. However, it doesn't mention permissions, rate limits, or error conditions.

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 perfectly concise: two sentences with zero waste. The first sentence states the purpose clearly, and the second sentence (in bold) provides crucial behavioral information about replacement. Every word earns its place, and the structure is front-loaded with the core purpose.

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 this is a mutation tool with no annotations and no output schema, the description does an adequate job but has gaps. It explains the replacement behavior well, but doesn't cover what happens on success/failure, what permissions are needed, or what the response contains. For a tool that modifies pipeline configurations, more context about the impact would be helpful, though the replacement warning is valuable.

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, meaning no parameters need documentation. The description appropriately doesn't discuss parameters, which is correct for a tool with no parameters. It focuses instead on the behavioral semantics of the update operation, which is exactly what's needed.

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: 'Update a given pipeline configuration to change it's processors or their order.' It specifies the verb ('update'), resource ('pipeline configuration'), and what can be changed ('processors or their order'). However, it doesn't explicitly distinguish this from sibling tools like 'update_logs_config_pipeline_orders' or 'create_logs_config_pipelines', which would be needed for a perfect score.

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. There's no mention of prerequisites, when-not-to-use scenarios, or comparison with sibling tools like 'create_logs_config_pipelines' or 'delete_logs_config_pipeline'. The note about replacement behavior is useful but doesn't address usage context relative to other tools.

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