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 of behavioral disclosure. It only states the action ('List') without detailing whether this is a read-only operation, if it requires specific permissions, what the output format might be, or if there are rate limits or pagination. This leaves significant gaps for a tool that likely returns a list of resources.

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, clear sentence with no wasted words. It is front-loaded with the core action and resource, making it efficient and easy to parse, though its brevity contributes to gaps in other dimensions like usage guidelines and behavioral transparency.

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 listing resources (which often involves pagination, filtering, or sorting), the lack of annotations, no output schema, and no sibling differentiation, the description is incomplete. It fails to provide necessary context about how the listing works, what is returned, or how it differs from similar tools, making it inadequate for effective tool selection and 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% coverage, so no parameter documentation is needed. The description does not mention any parameters, which is appropriate given the empty schema. It adds no semantic value beyond the schema, but since there are no parameters, this does not create a gap.

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 'List Synthetics tests' clearly states the verb ('List') and resource ('Synthetics tests'), making the basic purpose understandable. However, it lacks specificity about scope (e.g., all tests, filtered, paginated) and does not distinguish from sibling tools like 'search_synthetics_tests' or 'get_synthetics_tests', which could serve similar purposes.

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. With sibling tools like 'search_synthetics_tests' and 'get_synthetics_tests' available, there is no indication of differences in functionality, filtering capabilities, or appropriate contexts for use, leaving the agent without necessary decision-making information.

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