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. While it correctly indicates a destructive operation ('Delete'), it doesn't disclose critical behavioral traits like whether deletion is permanent, what permissions are required, if there are confirmation prompts, rate limits, or what happens to dependent resources. For a destructive tool with zero annotation coverage, this is inadequate.

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 directly states the tool's purpose. It's front-loaded with the key action ('Delete') and contains no unnecessary words or redundant 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 deletion tool with no annotations, no output schema, and no parameters, the description is insufficient. It doesn't explain what 'Confluent resource' means, what types can be deleted, whether deletion is reversible, what the response looks like, or error conditions. The agent lacks critical context for safe and correct usage.

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 parameters need documentation. The description mentions 'resource id' and 'account ID' which might imply parameters, but since the schema explicitly has no properties, this doesn't create confusion. The description adds no parameter information, which is acceptable given the empty schema.

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 verb ('Delete') and resource ('a Confluent resource'), specifying it's for a particular account via account ID. It distinguishes from generic delete tools by mentioning 'Confluent' and 'account', but doesn't explicitly differentiate from sibling tools like 'delete_integrations_confluent_cloud_account'.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, conditions, or what happens after deletion. It simply states what the tool does without contextual usage information.

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