slack_get_user_profile

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

With no annotations, the description carries full behavioral disclosure. It does mention the returned fields (display name, status, image URLs, custom fields), but it doesn't state whether the operation is read-only, any permission requirements, error behavior, or side effects. This is minimal transparency for a tool with no annotation support.

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 and well-structured with an Args/Returns layout. The main purpose is front-loaded in the first sentence, and the parameter details are organized without unnecessary verbosity.

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?

The tool is simple (2 params) and has an output schema, which covers return structure. However, the description omits potential error conditions, prerequisites (e.g., valid Slack token), or usage context relative to other profile-related tools. For a basic get operation, it's mostly adequate but could be more complete.

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 coverage is 0%, so the description must compensate. It provides meaningful explanations for both parameters: user_id includes the expected format ('starts with U, W, or B') and include_labels clarifies its purpose. This goes beyond the bare schema and helps the agent invoke correctly.

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?

States a specific verb and resource ('Get a Slack user's profile information'), clearly identifying the tool's function. It doesn't differentiate from the sibling slack_get_user_info, which could be confusing, but the name and description are not tautological.

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 on when to use this tool versus alternatives like slack_get_user_info. The description simply states what it does without any conditions, exclusions, or mention of alternative tools.

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