post_to_channel

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

No annotations, but description discloses that the message goes out as the token's member and appears live. This adds behavioral context beyond the implicit write operation.

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?

Two sentences, front-loaded with main purpose, no wasted words.

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 tool with two parameters, the description covers purpose, usage, behavior, parameters, and return value (posted message). Output schema missing but implied.

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 covers both parameters with descriptions, but description adds value by explaining channel_id resolution from list_channels and that body is visible to all members.

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 'post a message' and the resource 'team Comms channel', and distinguishes it from siblings like 'reply_in_channel' by noting it returns the posted message and appears as the token's member.

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 states when to use (tell team, share link, ask question) and provides prerequisite: resolve channel_id with list_channels and only works for member channels.

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