Retrieve the total number of active hosts in Datadog over a configurable time window, enabling host activity and capacity monitoring.
Get the total number of active hosts in Datadog (defaults to last 5 minutes)
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | Number of seconds from which you want to get total number of active hosts (defaults to 2h) |
Changes observed during successful MCP inspections.
v1.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does state the purpose and a default time window, but the stated default of 'last 5 minutes' contradicts the schema default of 7200 seconds (2 hours), which is a serious transparency issue for an agent relying on the description.
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 front-loaded sentence with no unnecessary text. It is appropriately sized for a simple count operation.
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 simple one-parameter read tool with no output schema, the description covers the core purpose. But the conflicting default and lack of sibling differentiation leave an agent with avoidable ambiguity.
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?
Schema coverage is 100%, so the parameter itself is well documented in the schema. However, the description's parenthetical default conflicts with the schema's default, adding confusion rather than meaning beyond the schema.
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?
States a specific verb and resource: getting the total number of active hosts in Datadog. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools like list_hosts, which would help an agent choose the right call.
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 implies a time-windowed count but gives no explicit guidance on when to use this tool versus alternatives such as list_hosts. It also does not explain any constraints or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.