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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description only needs to add context. It contributes the membership requirement and the @handle mention convention, which is real behavioral detail. Return behavior and visibility of the posted message are not described, but with annotations covering safety this is a minor gap.

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 tight sentences, front-loaded with the action and eligibility rule, followed by the two highest-value usage hints. No filler or redundant restatement.

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?

It is a mutation tool with six parameters, no output schema, and no mention of what is returned (e.g., message id) or how reply_to/token should be used in a follow-up flow. Core posting semantics are covered, but the reply and guest-token paths are left entirely to the schema.

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 the baseline is 3; the description earns an extra point by explaining the intent behind kind ("make it machine-readable" with the enumerated purposes) and data ("structured content"). It still says nothing about the token or reply_to parameters, which the schema documents only briefly.

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 in a room") plus a scoping prerequisite ("you're a member of"). It does not distinguish itself from the nearby message_thread_post or send_direct_message siblings, so an agent receives no explicit routing signal between them.

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?

Gives a membership prerequisite and implied usage for kind/data, but never says when to use room_post versus message_thread_post or send_direct_message. The guidance is implied by the feature list rather than an explicit when/when-not statement.

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