slack_usergroups_list

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

Without annotations, the description must convey behavioral traits. It only mentions routing and authentication scope, but fails to confirm read-only nature, side effects, rate limits, or output behavior. The name implies listing, but the description does not explicitly state it is safe or non-destructive.

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 but inefficient: it includes redundant routing details while omitting essential purpose and parameter semantics. It is under-specified rather than concise.

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?

Despite having an output schema, the description still fails to provide adequate context for invoking the tool correctly. Input semantics are missing, and the overall completeness is low given the tool's apparent simplicity.

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 single parameter 'arguments' is described only as a 'JSON string of arguments for the connector operation'. With 0% schema description coverage, the description should document what keys the JSON expects, but it does not. This leaves the agent with no clue about valid inputs.

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 usergroups_list' without providing a clear purpose or specific verb+resource. It does not explain what listing user groups entails or how it differs from similar tools.

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 given on when to use this tool versus alternatives like slack_usergroups_users_list. The description lacks any context about prerequisite conditions or typical use cases.

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