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 of behavioral disclosure. 'Send logs to intake' implies a write operation, but the description doesn't disclose any behavioral traits: no information about required permissions, rate limits, side effects, what 'intake' refers to, whether this is synchronous/asynchronous, or what happens on success/failure. This is a significant gap for a tool with zero annotation coverage.

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 with just three words: 'Send logs to intake'. It's front-loaded and wastes no words. Every word contributes to the core meaning, though that meaning is limited. This is an example of efficient communication within the constraints of minimal content.

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 complexity of a 'send' operation (likely involving data ingestion), the lack of annotations, no output schema, and minimal description, this is completely inadequate. The description doesn't explain what 'intake' is, what format logs should be in, authentication requirements, or expected outcomes. For a tool that presumably performs a write operation, this level of documentation is insufficient.

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). Since there are no parameters, the description doesn't need to add parameter semantics. The baseline for 0 parameters is 4, as the schema fully documents the absence of parameters, and the description doesn't need to compensate for any gaps.

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 'Send logs to intake' is a tautology that essentially restates the tool name 'logs_send'. It provides a verb ('Send') and resource ('logs') but lacks specificity about what 'intake' means or how this differs from other logging tools like 'logs_aggregate_analytics' or 'logs_search_events'. The purpose is vague and doesn't distinguish from siblings.

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 multiple sibling tools related to logs (e.g., 'logs_aggregate_analytics', 'logs_search_events', 'search_logs_events'), but the description doesn't indicate whether this is for ingestion, analysis, or other purposes. No context, exclusions, or prerequisites are mentioned.

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