slack_lookup_user

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

The description does not disclose any behavioral traits such as what data is returned, how the user is looked up (by email, ID, etc.), or any side effects. With no annotations, the description carries full burden but provides almost no 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 short and front-loaded, with a clear structure: operation name, routing context, then parameter. However, the conciseness comes at the expense of crucial information.

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 omits essential details about the tool's functionality. It fails to explain what the tool does or how to use it effectively, leaving the agent uninformed.

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 as a JSON string of arguments for the connector operation, but the description does not explain what keys or values are expected. With 0% schema coverage, the description should compensate, but it adds minimal value.

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 mostly restates the tool name as 'Slack connector operation lookup_user' without specifying what the operation actually does. The name 'lookup_user' suggests looking up a user, but the description lacks a clear verb and resource. It does not distinguish from siblings like slack_users_info or slack_list_users.

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. The description does not mention any context, prerequisites, or exclusions for using slack_lookup_user over other Slack user tools.

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