list-slos

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

No annotations provided, so the description carries the full burden. It describes listing but does not explicitly state that the operation is read-only, nor does it disclose pagination behavior, result ordering, or any side effects. The verb 'List' implies a read operation, but fails to provide explicit safety assurances.

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?

Single sentence, 10 words, no redundancy. Extremely concise and front-loaded with the key action 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 the tool has 5 parameters but no output schema, the description omits details about return format, pagination behavior (though limit/offset are in schema), and default ordering. Adequate for a simple list operation but leaves gaps for an agent to infer complete behavior.

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%, so the parameters are already described. The description adds a summary of filtering options (query, tags, IDs) correlating to the query, tagsQuery, and ids parameters, but does not add extra meaning beyond what the schema provides. Baseline of 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 identifies the tool's action ('List'), resource ('Service Level Objectives'), and the optional filtering capabilities (by query, tags, or IDs). It distinguishes itself from sibling tools like get-slo (single) and create-slo (creation) by focusing on listing with filtering.

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 guidance on when to use this tool versus alternatives (e.g., get-slo, get-slo-history, or search-based tools). The description only states what it does, not when it's preferred or when to avoid it.

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