datadog_slo_list

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

No annotations provided, so description carries full burden. States it is read-only, describes limit auto-pagination behavior, and mentions output format (YAML). Lacks mention of potential errors or rate limits, but sufficient for a read-only list 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?

Two sentences, front-loaded with purpose. No wasted words. Efficient and clear.

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; description only says 'Output is YAML' without detailing fields. Given the absence of annotations and output schema, more context on return structure would be beneficial. However, the filtering and pagination details are well covered.

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 coverage is 100% with parameter descriptions. Description adds value by grouping parameters as filters (tags, query, ids, metrics_query) and clarifying limit's special behavior (0 or omitted auto-paginates). This goes beyond the schema's individual descriptions.

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 'List Datadog Service Level Objectives' and specifies optional filters (tags, query, ids, metrics_query). It distinguishes from sibling tool datadog_slo_get by noting that the latter fetches one SLO's full definition by id.

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?

Explicitly mentions alternative tool datadog_slo_get for fetching a single SLO. Provides context on limit behavior (auto-paginate up to 10000). Could be more explicit about when not to use, but adequate for a list tool.

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