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

Annotations already declare a non-read-only, non-destructive, non-idempotent write. The description adds genuinely new behavior: other participants are notified, and the message is visibly marked as written through an agent. It does not state what happens on failure or whether repeated posts duplicate, but the added side-effect disclosure is substantial.

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?

Front-loads the action, then the notifications side effect, then the usage constraints, in three tight sentences with no filler. Slightly long, and the docs URL is a minor appendage, but every clause carries decision-relevant information.

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 two-parameter, non-destructive write with full schema coverage, the description covers purpose, side effects, and invocation boundaries. No output schema exists and none is needed for a post-only action.

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 100% for both parameters (forumId sourced from listMyConversations, message in the user's own words/language, plain text, 4000 max). The description echoes the 'in the user's own words and language' intent but adds no format or syntax beyond the schema, so baseline 3 applies.

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, as the user, in a conversation (forum) they take part in') and grounds it with three concrete examples (mission update, decision thread answer, profit split note). It is immediately distinguishable from siblings like readConversationTool and openRikmaConversationTool.

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 an explicit positive trigger ('ONLY when the user asked to say or record something') and two explicit exclusions ('never to think out loud', 'never to agree or refuse on their behalf'), plus the reason (approvals are the user's own click). This is the strongest form of routing guidance.

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