MCP Datadog Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't mention permissions required, whether deletion is reversible, what happens to dependent resources, or any rate limits. For a destructive operation with zero annotation coverage, this represents a significant gap in behavioral transparency.

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 exactly what the tool does without unnecessary words. It's appropriately sized for a simple deletion operation and front-loads the core action. Every word earns its place in this concise formulation.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what constitutes a 'service definition', how to identify which one to delete, what the deletion consequences are, or what the tool returns. Given the complexity of catalog operations and complete lack of structured behavioral information, the description should provide more context about this potentially impactful operation.

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 fully documents the absence of parameters. The description doesn't need to add parameter information, and it doesn't contradict the empty schema. The baseline for 0 parameters with full schema coverage is 4, as the description appropriately focuses on the action rather than parameters.

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 ('Delete') and target resource ('a single service definition in the Datadog Service Catalog'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'delete_catalog_entity' or 'delete_catalog_kind', which appear to target different resource types in the same catalog system.

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 other delete tools in the sibling list (e.g., delete_catalog_entity, delete_catalog_kind) that likely target different resources, but the description doesn't explain what distinguishes a 'service definition' from other catalog entities or when this specific deletion tool is appropriate.

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