MCP Datadog Server

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

No annotations are provided, so the description carries the full burden. It states 'Delete' which implies a destructive mutation, but doesn't disclose critical behavioral traits: whether deletion is permanent or reversible, what permissions are required, if there are side effects (e.g., cascading deletion of associated entities), or what the response looks like (success/failure indicators). 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 with zero waste. It's front-loaded with the key action ('Delete') and resource ('a single kind in Software Catalog'), making it immediately understandable. No extraneous information is included.

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?

Given the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address critical context: what a 'kind' is in the Software Catalog, how to specify which kind to delete (since there are 0 parameters), what happens on success/failure, or any safety warnings. For a deletion tool, this leaves too many unknowns 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 tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to explain parameters, but it implicitly suggests that the kind to delete must be identified elsewhere (e.g., in the tool name or context). Since there are no parameters, a baseline of 4 is appropriate—the description adequately conveys that no input is required beyond what's implied.

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 the resource ('a single kind in Software Catalog'), making the purpose unambiguous. However, it doesn't distinguish this tool from other deletion tools in the sibling list (e.g., delete_catalog_entity, delete_monitor), which would require specifying what a 'kind' is or how it differs from other catalog entities.

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 (e.g., needing to identify the kind first), consequences (e.g., whether deletion is permanent), or when not to use it (e.g., if the kind is in use). The sibling list includes create_catalog_kinds, suggesting a create-delete pair, but this relationship isn't explained.

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