get-synthetic-tests

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

Discloses what is returned (test names, types, status, locations, tags) but no annotations. Does not cover pagination behavior, rate limits, or authorization. Adequate for a read-only list tool but could be richer.

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?

Extremely concise: two sentences covering purpose, examples, and return values. No filler, front-loaded with verb and resource.

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 output schema, description adequately lists returned fields. Missing pagination details or default page size, but overall sufficient for a simple list 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 has 100% description coverage, so parameters are documented. Description adds little beyond the schema; example usage reinforces filter purposes but does not add new constraints.

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?

Description clearly states it lists Datadog Synthetic tests (API and browser). Provides example use cases. Does not explicitly distinguish from sibling 'get-synthetic-results', so not a 5.

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 example queries for when to use ('show all synthetic tests', 'what API tests exist', 'which tests are failing'). Lacks explicit when-not-to-use or alternative tools (e.g., get-synthetic-results).

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