slack_users_info

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

No annotations are provided, and the description offers no behavioral information such as whether the operation is read-only, requires authentication, or has side effects. The routing note is technical and does not compensate for the lack of behavioral transparency.

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 very short, but it is under-informative. While it is concise, it fails to include essential details, so its brevity is a drawback rather than a strength.

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 complexity of the tool (a connector with a generic arguments parameter), the description is severely incomplete. It does not explain the expected input structure, output format, or usage context, despite having an output schema available.

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?

With 0% schema description coverage, the description should explain the arguments parameter. It only says 'JSON string of arguments for the connector operation,' which adds minimal value. It does not specify what keys the JSON should contain (e.g., user ID), leaving the agent underinformed.

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 states it's a Slack connector operation 'users_info', which hints at retrieving user information, but it does not explicitly state what the tool does (e.g., 'Get details about a Slack user'). The purpose is inferred from the name rather than clearly articulated.

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 alternatives like slack_list_users or slack_lookup_user. There is no context about prerequisites 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.