slack_list_users

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

No annotations are provided, so the description must carry the full burden. It mentions routing and JWT scope but fails to disclose whether the tool is read-only, if pagination is supported, output format, or rate limits. Key behavioral traits are missing.

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 short (3 sentences) and covers routing and arguments without clutter. It is efficient but could be more informative without sacrificing brevity.

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 an output schema, return values need not be described. However, the description lacks essential context: what users are listed (all members? active only?), how to use arguments for filtering, and real-world usage examples. The tool is simple but the description is incomplete.

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?

The only parameter 'arguments' is described as a 'JSON string of arguments', adding some meaning beyond the bare schema (which has 0% coverage). However, it does not specify expected keys like cursor or limit, leaving the agent to guess the structure.

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 name 'slack_list_users' clearly indicates listing users from Slack. The description states it's a 'Slack connector operation' and explains the routing. However, it does not differentiate from sibling Slack user tools like slack_lookup_user or slack_users_info.

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 vs alternatives. No prerequisites or context provided (e.g., requires authentication, lists all workspace members). The agent must infer usage without explicit direction.

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