Get Slack User Info

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

Annotations already declare the tool safe (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds that it returns a user profile with id, name, email, title, timezone, and status, which is useful but not extensive beyond what annotations already imply.

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 succinct and well-structured: a one-sentence purpose, followed by a labeled Args section and a Returns section. Every sentence contributes value without redundancy.

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?

For a simple one-parameter read tool, the description covers purpose, parameter, and return shape. It lacks an explicit comparison to slack_lookup_user, but overall it provides sufficient context given the simple nature and strong annotations.

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?

Schema description coverage is 100%, and the description merely repeats the same parameter info ('user_id (string): Slack user ID (e.g. U012AB3CD)'). No additional semantic meaning is provided beyond the schema.

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 clearly states the verb and resource: 'Get detailed profile information for a specific Slack user by their user ID.' It is specific enough to differentiate from searching messages or channels, though it does not explicitly distinguish itself from the sibling 'slack_lookup_user'.

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?

Usage context is implied: the tool should be used when you have a Slack user ID and need detailed profile info. However, no explicit guidance is given on when to prefer this over alternatives like slack_lookup_user, and no exclusions are mentioned.

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