query-metrics

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

No annotations; description says returns data points with timestamps, but does not disclose side effects, permissions, or rate limits. Adequate for a read operation but not comprehensive.

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?

Two sentences: purpose in first, examples and syntax in second. No wasted words, front-loaded.

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?

No output schema but describes return type. Could better differentiate from sibling metric tools, but sufficient for a query tool.

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 covers all 3 parameters (100%). Description adds query syntax example, enhancing understanding beyond schema descriptions. Baseline 3 plus extra value.

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?

Clearly states the tool queries time-series metrics from Datadog, with concrete examples ('CPU usage over last hour', 'request rate for web service'). Distinguishes from siblings like aggregate-logs or get-hosts.

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?

Provides context for use (metric queries) but lacks explicit guidance on when not to use or alternatives among sibling metrics tools (get-metrics, get-metric-metadata).

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