MCP Datadog Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Delete' which implies a destructive operation, but doesn't specify whether this is reversible, what permissions are required, what happens to associated data, or any rate limits. For a destructive tool with zero annotation coverage, this leaves critical behavioral traits 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 a single, efficient sentence that directly states the tool's function with no wasted words. It's appropriately sized for a tool with no parameters and gets straight to the point without unnecessary elaboration.

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 destructive deletion tool with no annotations, no output schema, and no parameters, the description is insufficient. It doesn't explain what 'Agentless scan options' are, what gets deleted, whether deletion is permanent, what confirmation or side effects occur, or what the response contains. The context demands more completeness for safe agent 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, so the schema fully documents the absence of inputs. The description doesn't need to compensate for parameter documentation gaps. However, it could theoretically mention that no parameters are required, though this isn't necessary given the schema coverage.

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 clearly states the action ('Delete') and resource ('Agentless scan options for an AWS account'), making the purpose understandable. However, it doesn't distinguish this tool from sibling deletion tools (like 'delete_agentless_scanning_accounts_aws' or 'delete_integration_aws'), which would require more specificity about what 'scan options' entails versus deleting entire accounts.

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 for AWS account management (create_agentless_scanning_accounts_aws, update_agentless_scanning_accounts_aw, get_agentless_scanning_accounts_aw), but the description doesn't indicate prerequisites, dependencies, or when deletion is appropriate versus other operations.

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