datadog_slo_list

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

No annotations provided. Description adds pagination behavior (limit 0 or omitted auto-paginates up to 10000) and output format (YAML), but does not disclose read-only nature, authentication needs, or rate limits. Adequate but minimal beyond schema.

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?

Three sentences, front-loaded with purpose, followed by key behavioral detail (pagination) and supplementary info (CLI mirror, output format). No wasted words, highly efficient.

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 list tool with 5 optional parameters and no output schema, the description explains pagination and output format but does not outline the return structure (e.g., array of SLO objects). Lacks completeness for an agent to fully understand output without schema.

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 description coverage is 100% with detailed parameter descriptions. The tool description adds value only for the `limit` parameter (pagination behavior), which replicates schema info. No additional semantics for other parameters. Baseline 3 is appropriate.

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 'List Datadog Service Level Objectives' with a specific verb and resource. It also adds key details like auto-pagination up to 10000 and YAML output, distinguishing this listing tool from the sibling `datadog_slo_get` which retrieves a single SLO.

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?

No explicit guidance on when to use this tool versus alternatives like `datadog_slo_get`. The purpose implies listing, but the description does not direct the agent to use this for batch retrieval and the sibling for single SLO lookup.

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