slack_list_channel_members

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only mentions routing scope (JWT, tenant, company) but does not describe whether the tool is read-only, has side effects, rate limits, or pagination. The core behavior of listing members is not explained.

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 concise (three sentences) and includes routing and argument info, but the first sentence is a tautology. It is not well-structured for quick understanding; key purpose information is missing.

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?

Although an output schema exists, the description does not mention return values or behavior. It lacks purpose, usage, and parameter detail. The routing info is helpful but insufficient to make the tool fully understandable.

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 input schema has one parameter (arguments) with zero schema-level description. The description adds that it is a 'JSON string of arguments for the connector operation' but does not specify what keys or values are expected (e.g., channel ID). This is insufficient given the low schema coverage.

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 merely restates the tool name as 'Slack connector operation list_channel_members' without clarifying what the tool does (e.g., listing members of a Slack channel). The purpose is only implied by the name, but the description fails to explicitly state the verb and resource, making it vague.

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 is provided on when to use this tool versus alternative tools like slack_list_channels or slack_list_files. The description does not mention any context, prerequisites, or scenarios where this tool is appropriate.

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