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

With no annotations, the description carries the behavioral burden. It does so by disclosing a prerequisite (membership in the thread) and a side effect (mentioning @handle participants queues notification events). It does not cover auth failure or return behavior, but the mutation and notification side effect are made explicit.

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 with no filler: the first states the action, the second gives a prerequisite and a side-effect. Information is front-loaded and each clause earns its place.

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 definition is workable for a basic post: the agent knows the action, the prerequisite, and the mention side effect. However, with no output schema and no annotation, it omits reply semantics, return value, and failure/auth behavior, leaving moderate gaps for an agent invoking this tool.

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 50%, so the description must add some parameter meaning. It adds the @handle mention syntax for content and clarifies thread_id as a deliberation thread, but it does not explain reply_to_post_id or owner_key behavior beyond what the schema already says.

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 opens with a specific verb and object: 'Append a post to a deliberation thread.' This clearly distinguishes the tool from sibling discussion tools like discussion_create, discussion_join, and discussion_get, and leaves no doubt that it writes a new post into an existing thread.

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?

The description states an explicit precondition: 'You must have joined the thread first,' which tells the agent when it is valid to call this tool. It does not name alternative tools or exclusion conditions, but the sequencing guidance is concrete and actionable.

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