slack_set_status

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

There are no annotations, so the description carries the burden of behavioral disclosure. It reveals the mutation action but does not describe side effects (e.g., whether existing status is replaced, how optional emoji is handled), authentication needs, or response behavior. This lack of detail may leave the agent uncertain about the operation's full implications.

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 a single clear sentence with no unnecessary words. It is front-loaded and efficiently conveys the tool's purpose.

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 setter tool with no output schema and no behavioral notes, the description provides the core action but leaves gaps: optional emoji behavior, whether the status is overwritten or appended, and expected return values are not addressed. This is adequate but not comprehensive.

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 100% with descriptions for both parameters ('Status text' and 'Status emoji shortcode'). The description adds no additional semantic meaning beyond restating these fields, so the baseline of 3 is appropriate.

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 action ('Set') and the resource ('the authenticated user's status text and emoji'). It is specific enough to distinguish from sibling tools like slack_send_message or slack_create_channel, which deal with messaging or channel management.

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?

The context of use is clear: this tool is for updating the current user's status. However, it does not explicitly mention when not to use it or provide alternative tools, though no direct alternative exists among siblings. The clarity of the resource implies the use case effectively.

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