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 'fetch' which implies a read operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or what 'data' includes (e.g., status, results). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 sentence that directly states the tool's action. It's front-loaded and wastes no words, though it could be slightly more informative. Given the lack of parameters, this conciseness is efficient.

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 no annotations, no output schema, and a vague description, this tool is inadequately documented. The description doesn't explain what 'on demand task' means, what data is returned, or any behavioral context. For a tool in a complex environment (as seen from sibling tools), this leaves the agent with insufficient information to use it correctly.

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% coverage, so no parameters need documentation. The description doesn't add parameter details, which is appropriate here. Baseline is 4 since there are no parameters to explain, and the description doesn't contradict or confuse this.

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 'Fetch the data of a specific on demand task' states a verb ('fetch') and resource ('data of a specific on demand task'), but is vague about what constitutes 'on demand task' and doesn't differentiate from sibling tools like 'get_agentless_scanning_accounts_aws' or 'create_agentless_scanning_ondemand_aws'. It provides a basic purpose but lacks specificity.

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 prerequisites, context, or distinguish it from related tools like 'create_agentless_scanning_ondemand_aws' (which might create such tasks) or other 'get_' tools in the list. Usage is implied but not explicitly stated.

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