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. 'Delete' implies a destructive operation, but the description doesn't specify whether this requires special permissions, whether deletion is permanent, what happens to associated resources, or what the response looks like. For a destructive tool with zero annotation coverage, this is a significant gap.

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 states the core action without any wasted words. It's appropriately sized for a simple deletion operation and front-loads the 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 destructive operation with no annotations, no output schema, and multiple similar sibling tools, the description is inadequate. It should clarify what type of application key is being deleted, any prerequisites or permissions needed, and how this differs from other deletion tools. The current description leaves too many open questions for safe tool 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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to add parameter information, and it doesn't attempt to do so. Baseline 4 is appropriate for zero-parameter tools where the schema handles all documentation needs.

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 'Delete an application key' clearly states the verb ('Delete') and resource ('application key'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_current_user_application_key' or 'delete_service_account_application_keys', which appear to target specific types of application keys.

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 multiple deletion tools for application keys in the sibling list (delete_current_user_application_key, delete_service_account_application_keys), the agent has no indication whether this is a general deletion tool or specific to certain contexts.

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