MCP Datadog Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description reveals nothing about whether this is a read or write operation, what permissions are required, whether it has side effects, rate limits, or what format the results return. This leaves the agent completely in the dark about how to use the tool safely and effectively.

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 extremely concise ('Metrics: query timeseries'), but this brevity comes at the cost of being under-specified rather than efficiently informative. While it's front-loaded with the core concept, it lacks the necessary detail to be truly helpful, making it more sparse than optimally concise.

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 that this is a query tool with no annotations, no output schema, and a minimal description, the description is completely inadequate. For a tool that presumably returns timeseries data, the description should explain what kind of data it returns, any required context, or how it differs from similar query tools. The current description fails to provide any meaningful context.

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 tool has 0 parameters with 100% schema description coverage. Since there are no parameters to document, the description doesn't need to compensate for any gaps. The baseline for 0 parameters is 4, as there's no parameter information to provide beyond what's already covered in the schema.

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 'Metrics: query timeseries' is a tautology that essentially restates the tool name. It mentions 'query' as a verb and 'timeseries' as a resource, but lacks specificity about what kind of metrics or timeseries data it queries. Compared to siblings like 'metrics_query_scalars' or 'query_timeseries', it doesn't clearly differentiate its purpose.

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 are multiple sibling tools like 'metrics_query_scalars', 'query_timeseries', and various analytics aggregation tools, but the description offers no comparison or context about when this specific tool is appropriate.

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