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 for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't specify required permissions, whether this is idempotent, what happens on conflict, or what the response contains. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects undocumented.

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 ('Create an AuthN Mapping.') but this brevity comes at the cost of being under-specified rather than efficiently informative. While it's not verbose, it fails to provide necessary context that would help the agent understand what's being created. The single sentence doesn't earn its place by adding value beyond the tool name.

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 this is a mutation tool with no annotations, no output schema, and a vague description, the description is incomplete. It doesn't explain what an AuthN Mapping is, what the creation entails, what permissions are needed, or what the tool returns. For a tool that presumably creates security/auth-related resources, this leaves significant gaps in understanding.

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 (empty schema), so there are no parameters to document. The description doesn't need to compensate for missing parameter information. A baseline of 4 is appropriate since the schema fully covers the non-existent parameters, though the description could theoretically mention that no parameters are required.

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 'Create an AuthN Mapping' is a tautology that restates the tool name without adding meaningful context. While it indicates a creation action, it doesn't specify what an 'AuthN Mapping' is, what resource it creates, or how it differs from similar tools like 'create_authn_mappings' (plural) or 'update_authn_mapping' among siblings. This provides minimal differentiation beyond the name itself.

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 are no mentions of prerequisites, appropriate contexts, or comparisons with sibling tools like 'get_authn_mappings', 'update_authn_mapping', or 'delete_authn_mapping'. The agent receives no help in determining when this specific creation tool is appropriate.

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