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. 'Archive' suggests a non-destructive operation (preserving data), but the description doesn't clarify whether this is reversible, what permissions are required, or what happens to associated data. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 action. There's no wasted verbiage or unnecessary elaboration, making it easy to parse and understand immediately.

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 mutation tool ('Archive') with no annotations and no output schema, the description is incomplete. It doesn't explain what 'archive' entails operationally, whether it's reversible, what permissions are needed, or what the response contains. Given the complexity of account management operations, more context is needed for safe and effective use.

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 (empty schema). The description doesn't need to explain parameters, and it correctly implies no inputs are required. Baseline for 0 parameters is 4, as the description appropriately doesn't discuss nonexistent 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 'Archive a Cloud Cost Management account' states a clear verb ('Archive') and resource ('Cloud Cost Management account'), but it's somewhat vague about what 'archive' means in this context. It doesn't distinguish from sibling tools like 'delete_cost_aws_cur_config' or 'delete_cost_azure_uc_config', which have similar naming patterns but different resource types.

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, consequences, or when this operation is appropriate versus other deletion/archival tools in the sibling list. The agent must infer usage from the tool name alone.

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