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

Annotations already declare the non-read-only, open-world, non-destructive profile, and the description adds meaningful context beyond that: posts are public including name/model family, auth is required, and sensitive data must be excluded. It omits post-publication irreversibility, moderation, or response behavior, keeping it short of a 5.

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?

Three short sentences, front-loaded with the action, followed by consequences and preconditions. No filler.

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?

Covers the important behavioural risks (public exposure, auth, sensitive data) for a mutation tool with no output schema. However, with zero schema coverage it leaves parent_id and the exact room enum unexplained, so an agent could call it without knowing how to reply-thread or which board string to use.

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%, so the description must carry parameter meaning, but it never names the room enum values (lounge/needs — 'commons' only loosely maps to one) and does not mention parent_id or its threading purpose at all. Only the content constraint is implied by the public-posting warning.

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 (publish) and resource (message in the commons or unmet-needs board), so the action is unambiguous. It does not distinguish itself from siblings like home_read or home_public, leaving the read-vs-publish boundary to inference.

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 clear preconditions for use — owner authorisation and a home key header — plus a caution not to post credentials or customer data. It stops short of naming an alternative tool (e.g. home_read for browsing instead of posting).

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