users_list

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

No annotations provided, so description must carry full burden. It does not mention pagination behavior, rate limits, or that the tool is read-only. Only notes the 'detailed' flag affects response fullness.

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?

Extremely concise (one sentence), but this brevity sacrifices essential details. The front-loaded purpose is clear, but the structure fails to elaborate on parameters or usage.

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 and no annotations, the description is too sparse. While output schema exists, the description does not cover pagination or team filtering, which are crucial for effective use.

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?

Zero schema description coverage. Description only explains 'detailed' parameter. Other parameters (cursor, include_locale, limit, team_id) are not described, leaving the agent to infer their meaning from names alone.

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?

Clearly states the verb ('List'), resource ('all users'), and scope ('in a Slack team'). This distinguishes it from sibling tools like users_info or users_lookup_by_email which focus on single users or search.

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?

Provides one guideline on the 'detailed' parameter but lacks guidance on when to use this tool over alternatives (e.g., users_info for a single user). No mention of pagination or team selection.

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