post_message

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

Discloses that action_flag is stored but display-only (no action performed). However, no annotations are provided, and the description does not cover other behavioral aspects like idempotency, rate limits, or potential side effects beyond append-only.

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 brief sentences that efficiently convey core purpose and a key nuance. 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?

Adequately describes the tool's main function and a behavioral quirk, but lacks details on response format (though output schema exists), error conditions, and parameter constraints. Sufficient for a simple append operation but not exhaustive.

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?

With 0% schema description coverage, the description must compensate, but it only explains action_flag's behavior. The other parameters (topic, sender, body) are left undefined, providing insufficient guidance for correct invocation.

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?

Clearly states the verb 'Append one message' and the resource 'coordination-bus blackboard', and specifies append-only behavior. Distinguishes from sibling tools like read_messages, release_lane, etc., which have different purposes.

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?

Implied usage context from sibling tool names (e.g., read_messages for reading), but no explicit when to use or when not to use. Lacks guidance on prerequisites or alternatives.

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