Restore archived Datadog cases to active status for continued monitoring and management operations.
Unarchive case
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "create_case_unarchive"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description offers no behavioral information beyond the basic action implied by 'unarchive'. With no annotations provided, the description fails to disclose whether this is a read-only or destructive operation, what permissions are required, whether it's idempotent, or what happens if the case isn't archived. For a mutation tool with zero annotation coverage, this is a critical gap in behavioral disclosure.
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 maximally concise at two words. Every word earns its place by specifying both the action and target resource. There's no wasted verbiage, repetition, or unnecessary elaboration. The structure is front-loaded with the essential 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 mutation tool with no annotations, no output schema, and zero parameters, the description is inadequate. While conciseness is appropriate given the simple parameter situation, the description fails to provide necessary context about what 'unarchiving' means operationally, what the expected outcome is, or any behavioral constraints. The agent would need to guess about the tool's effects and requirements.
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?
With 0 parameters and 100% schema description coverage, the description doesn't need to compensate for missing parameter documentation. The schema already fully documents that no inputs are required. The description appropriately doesn't waste space discussing nonexistent parameters, though it could mention that the tool likely operates on a pre-selected or contextually identified case.
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 'Unarchive case' is essentially a tautology that restates the tool name 'create_case_unarchive'. It specifies the verb ('Unarchive') and resource ('case'), but provides no additional context about what 'unarchiving' entails or what type of case is being referenced. While it distinguishes from sibling 'create_case_archive', it lacks specificity about the operation's scope or effect.
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 zero guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., that a case must already be archived), when-not-to-use scenarios, or related tools like 'create_case_archive' for the opposite operation. The agent receives no contextual usage information beyond the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.