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 but offers none. It doesn't indicate whether this is a read-only operation, what authentication is required, whether it has side effects, rate limits, or what format/details are returned. 'Get' implies retrieval but lacks any behavioral context about the operation's characteristics or constraints.

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 ('Get the device details.') but under-specified rather than efficiently informative. While it's a single sentence with no wasted words, it fails to provide necessary context that would help the agent understand what 'ndm' means or what details are retrieved. Conciseness shouldn't come at the cost of essential information.

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?

For a tool with no parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'ndm' stands for, what constitutes 'device details', whether this retrieves a specific device or current device, or what the return format looks like. The agent would need to guess about the tool's behavior and output based solely on the vague description.

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 (empty schema). The description doesn't need to explain parameters since none exist, and it correctly avoids mentioning any. This meets the baseline expectation for parameterless tools, though it doesn't add value beyond what the schema already indicates.

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 'Get the device details' is a tautology that essentially restates the tool name 'get_ndm_device'. It provides a generic verb ('Get') and resource ('device details') but lacks specificity about what 'ndm' refers to or what kind of device details are retrieved. While it distinguishes from siblings by focusing on devices, it doesn't clarify scope or differentiate from similar tools like 'get_ndm_devices' (plural).

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, context, or comparison to sibling tools like 'get_ndm_devices' (which appears to retrieve multiple devices). The agent receives zero usage instructions beyond the basic action implied by the name.

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