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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds real context beyond them — posting happens immediately with no confirmation step, the bot must be a channel member, and it discloses markdown rendering support. It stops short of saying whether a sent message can be edited or recalled, which would matter for a destructive write.

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?

Front-loaded with the action and scope, then guardrails, then the alternative, then a formatting footnote. Dense but every sentence carries operative information; the rendering sentence is useful but could be trimmed if space were tight.

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?

With no output schema, the description does not say what comes back (message ts, permalink) — relevant since the returned ts is needed to thread or reference the message later. Otherwise the guardrails, permission constraint, and alternative routing make it complete enough to invoke safely.

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%, so baseline is 3, but the description adds selection meaning for channel_id ('only channels the bot has been invited to; use list_slack_channels to find ids') and confirms thread_ts is optional. team_id and text are left entirely to the schema, so it does not fully compensate where the schema is thin.

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 ('Post a message to a Slack channel'), the posting identity ('as YouSpot'), timing ('right now'), and the thread variant. An agent can immediately distinguish this from draft_slack_message without opening either schema.

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?

Explicitly bounds when it may be used ('Only for text the user already approved word for word... or an agent delivering its own report') and names the alternative with the selecting condition ('When the user asks you to write, draft or prepare... use draft_slack_message instead: nothing posts until they tap Send'). It also states the prerequisite that the bot must be invited and points to list_slack_channels for ids.

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