list_list_items

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

With no annotations provided, the description carries the disclosure burden. It does disclose pagination behavior and a required scope, which is useful. However, it does not explain how pagination works (e.g., cursor-based, whether all pages are automatically fetched), what the response format is, or explicitly state that this is a non-mutating 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?

The description is a single concise sentence that front-loads the core action and resource, then adds pagination and scope requirements. No filler or redundant phrasing is present.

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 simple read-only list tool with two parameters and full schema coverage, the description provides the key operational facts: what is fetched, that pagination is involved, and what scope is needed. It does not describe response structure or pagination mechanics, but this is a relatively simple tool and the main invocation requirements are 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 description coverage is 100%: list_id is described as 'List ID' and limit as 'Max items per page (default 100)'. The description adds context about pagination and fetching all items but does not substantially enrich parameter semantics beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('Fetch') and names the exact resource ('all items in a Slack List'), also noting pagination. This clearly distinguishes it from sibling tools like get_list_item (singular item) and create_list_item (creation), so an agent can tell them apart.

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 when to use the tool: when you need all items in a Slack List, and it provides a prerequisite ('Requires lists:read scope'). However, it does not explicitly contrast it with alternatives or mention cases where get_list_item or other list-related tools would be more appropriate.

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