post_new_message_api_v1_channels

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

With no annotations, the description should disclose behavioral traits. It does not mention whether this tool modifies existing messages, requires authorization, or has rate limits. The bare phrase 'Post New Message' only implies creation, without details on side effects or constraints.

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 extremely concise (3 words), but it sacrifices informativeness. While brevity is good, it omits crucial context that could be added without becoming verbose.

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 description is insufficient for the tool's complexity (7 parameters, output schema). It does not explain the outcome, error conditions, or relationship to sibling tools. The output schema exists, but the description doesn't hint at the return value format or success/failure indicators.

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%, and the description adds no parameter information. Required parameters 'id' and 'content' are not explained (e.g., 'id' likely channel ID, but not stated). Optional parameters like 'data', 'meta', 'parent_id' are completely undocumented, leaving the agent to guess their semantics.

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 'Post New Message' clearly indicates the action (post) and the object (new message), but lacks specificity about the context (channel, thread, etc.). The tool name includes 'channels', but the description does not mention this, making it ambiguous compared to siblings like 'post_webhook_message'.

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 is provided on when to use this tool versus alternatives such as 'update_message_by_id' or 'send_chat_message_event'. The description fails to clarify the intended use case or prerequisites (e.g., existing channel, permissions).

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