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 mentions retrieving details but doesn't disclose behavioral traits like whether this is a read-only operation, what permissions are required, how errors are handled, or what format the response takes. The description is too minimal for a tool that presumably returns structured case data.

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 extremely concise at just 7 words, front-loading the core purpose with zero wasted language. Every word earns its place by specifying the action, resource, and key parameter.

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 tool with no annotations, no output schema, and presumably returning case details, the description is incomplete. It doesn't explain what 'details' includes, the response format, error conditions, or authentication requirements. Given the complexity of case data in this system (with sibling tools for case attributes, priority, status, etc.), more context is needed.

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 description explicitly mentions the 'case_id' parameter, adding semantic meaning beyond the empty input schema. With 0 parameters and 100% schema description coverage, the baseline is 4. The description compensates by indicating what the single expected input should be, though it doesn't specify format or constraints.

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 states the tool's purpose as retrieving case details using a case_id parameter, which is clear but basic. It specifies the verb 'Get' and resource 'case details', but doesn't distinguish from sibling tools like 'get_cases' (plural) or provide any scope or depth information about what 'details' includes.

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. The description doesn't mention sibling tools like 'get_cases' (which appears to list multiple cases) or 'create_cases', nor does it specify prerequisites, error conditions, or appropriate contexts for usage.

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