get-metrics

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

No annotations are provided, so the description carries the full burden. It mentions the tool searches by name pattern but does not disclose behavioral traits such as whether it is read-only, authentication requirements, rate limits, or pagination behavior. The description lacks sufficient transparency for a tool without annotations.

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 concise, containing two sentences and a parenthetical example. It is front-loaded with the primary purpose and quickly provides usage context. No extraneous information.

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 tool with one parameter and no output schema, the description covers the main purpose and parameter usage. However, it lacks details on return format, possible empty results, or performance considerations. It is adequate but not comprehensive.

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 schema has 0% description coverage for the single parameter 'q'. The description compensates by explaining that 'q searches metric names' and provides an example. While it adds meaning beyond the schema, it could be more precise about pattern matching (e.g., wildcard support).

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 tool searches for available Datadog metrics by name pattern, using the verb 'search' and specifying the resource. It provides examples that help distinguish from possible data querying tools like 'query-metrics', though not explicitly differentiating.

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 indicates when to use the tool ('to discover metrics') but does not explicitly state when not to use it or mention alternative tools like 'query-metrics' for fetching metric values. The usage context is implied rather than explicit.

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