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 retrieving 'last 150 test results summaries,' which implies read-only behavior, but fails to disclose critical details like authentication requirements, rate limits, error handling, or the format of the summaries. This leaves significant behavioral gaps for the agent.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core action and resource, making it highly concise and well-structured.

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 of retrieving test results (which may involve data formats, pagination, or filtering), the description is insufficient. With no annotations, no output schema, and minimal behavioral details, it lacks completeness. The agent would struggle to understand the full context of use and response handling.

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 baseline is high. The description adds no parameter information, but since there are no parameters to document, this is acceptable. It implies the tool operates on a specific test, but without parameters, this is more about context than semantics.

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') and resource ('last 150 test results summaries for a given Synthetic API test'), making the purpose specific. However, it does not explicitly differentiate from sibling tools like 'get_synthetics_test_results_v1' or 'get_synthetics_tests_browser_results_v1_2', which might serve similar purposes, so it falls short of 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, such as other test result retrieval tools in the sibling list. It lacks context about prerequisites, timing, or any exclusions, leaving the agent without usage direction.

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