slack_users_set_presence

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

No annotations exist, and the description does not disclose whether the tool changes the caller's own presence or someone else's, whether it is idempotent, or any side effects. This is a critical gap for a mutation tool.

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 but includes irrelevant routing details ('Routes through /api/tools/invoke...') that do not help an agent decide when to use the tool. It is not optimally concise for decision-making.

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 fails to indicate what the tool returns or any preconditions. With no annotations and a single parameter, the description leaves the agent completely uninformed about the tool's behavior.

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 sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation', which merely echoes the schema. With 0% schema description coverage, the description adds no meaningful guidance on how to structure the arguments.

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 only restates the tool's name and indicates it's a Slack connector operation. It does not clarify what 'set presence' means (e.g., set status to away or active) or specify the resource being modified.

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 when-to-use or when-not-to-use guidance is provided. There is no mention of alternatives or context distinguishing it from sibling Slack tools like slack_set_channel_purpose or slack_users_info.

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