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. It states this is a deletion operation (destructive), but doesn't mention permissions required, whether deletions are permanent/reversible, rate limits, error handling for partial failures, or what happens if app IDs are invalid. 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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the core action.

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 bulk deletion tool with no annotations, no output schema, and an empty input schema that contradicts the description's implication of parameters, the description is inadequate. It doesn't explain how to provide app IDs, what the response looks like, or critical behavioral aspects like safety confirmations or error handling.

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, so there are no parameters to document. The description implies input ('from a list of app IDs') but doesn't specify how this list is provided given the empty schema. Baseline 4 is appropriate for zero parameters, though the mismatch between description and schema is noted.

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 multiple apps') and resource ('apps') with the specific capability of handling multiple items in a single request. It distinguishes from the sibling 'delete_app_builder_app' which likely handles single deletions, though this distinction isn't explicitly stated.

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 is provided on when to use this tool versus alternatives like 'delete_app_builder_app' for single deletions or other deletion tools. The description mentions bulk deletion but doesn't specify prerequisites, constraints, or typical use cases.

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