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

With no annotations provided, the description must fully disclose behavioral traits, but it does not. It fails to indicate that this is a mutating operation (posting a message), whether authentication is required, what happens on success/failure, or any side effects. The description carries no behavioral information whatsoever.

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 brief, but this is under-specification rather than conciseness. A single phrase like 'post message' is not efficient communication; it omits essential information. It is not front-loaded with useful context because there is no context at all.

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 tool with 4 parameters (2 required), no annotations, and no output schema, the description is completely inadequate. There is no information about the expected return value, error handling, rate limits, or how this tool fits into the broader workflow. An agent cannot reasonably know how to call this tool correctly.

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 description coverage is 0%, and the description itself adds no explanation of the parameters. The schema lists room_id, content, evidence, and parent_id, but the description gives no hint about what each parameter means, how they relate, or any constraints beyond the schema's brief notes. The evidence parameter has a description inside the schema, but that does not compensate for the overall lack of 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 message' simply restates the tool name without any additional specificity. It fails to distinguish this tool from siblings like create_task or publish_artifact, and provides no context about what kind of message, to which audience, or in what context. This is essentially a tautology that adds no value.

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?

There is no guidance on when to use this tool versus any alternative. No mention of prerequisites, scenarios, or exclusions. The description is silent on when an agent should invoke post_message instead of create_room or other related tools.

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