list-services

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

No annotations are provided, so the description carries full burden for behavioral traits. It only states the action with filtering, omitting crucial details like pagination behavior, response structure, or whether the list is scoped (e.g., all services vs. user-scoped). This is insufficient for a read operation.

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?

A single, front-loaded sentence that clearly states the verb and resource. No extraneous words. Every word earns its place.

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 and moderate parameter count (5), the description is too minimal. It lacks information about return value format, pagination details, rate limits, or any usage scope. The complexity of the Datadog Software Catalog is not addressed.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no extra meaning beyond the schema, just repeating 'with filtering'. It does not clarify parameter combinations or ordering, but is not misleading.

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 lists services from Datadog Software Catalog with filtering. It uses a specific verb-resource combination ('list services'), and while siblings exist (e.g., list-hosts, list-containers), none target the same resource, so differentiation is adequate but not explicit.

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 usage (listing services with filtering) but provides no guidance on when to use this tool vs alternatives (e.g., get-service-definition for a single service), nor any prerequisites or context. This is a missed opportunity for clarity.

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