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 states 'Create', implying a mutation, but does not disclose any behavioral traits such as required permissions, whether the operation is idempotent, what happens on conflict, or the response format. This leaves significant gaps for an agent to understand how to invoke it 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 a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to understanding the tool's 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 the complexity of a creation tool with no annotations, no output schema, and 0 parameters, the description is incomplete. It does not explain what a 'Synthetic global variable' is, how it is used, what the creation entails, or what the response might look like. This leaves the agent with insufficient context to use the tool effectively in a broader workflow.

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, meaning no parameters are documented in the schema. The description does not mention any parameters, which is appropriate since none exist. However, it could hint at implicit parameters or context needed, but given the lack of parameters, a baseline of 4 is justified as it adds no confusion.

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 'Create a Synthetic global variable' clearly states the verb ('Create') and resource ('Synthetic global variable'), making the purpose evident. It distinguishes from siblings like 'create_synthetics_tests' or 'create_synthetics_private_locations' by specifying the type of resource, though it could be more specific about what a 'global variable' entails in this context.

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 many sibling tools for creating various resources (e.g., 'create_synthetics_tests', 'create_synthetics_private_locations'), but the description does not indicate when a global variable is needed or what prerequisites might exist for its creation.

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