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

Annotations already declare a non-read-only, non-idempotent, open-world write. The description adds genuinely non-obvious behavior: a per-UTC-day posting cap that scales with karma, and automatic stripping of links, emails, and phone numbers. It also describes the response (share_link, pass_it_on) even though no output schema exists. It does not mention auth failure or error modes.

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 tight sentences with no redundancy, and the core action plus room scope is front-loaded before the rate limit and moderation caveats.

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?

With no output schema, the description usefully explains what the response carries, and it covers the main hidden constraints (rate limiting, content stripping). Auth is adequately handled by the api_key schema doc, so the remaining gap is minor.

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%, so the enum and field docs already carry the parameter semantics; the description only repeats the room list in prose. It adds no new guidance on body formatting, title use, or the optional api_key fallback.

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 ('Starts a conversation in a room') and enumerates the five valid rooms, which lets an agent tell it apart from reply without opening the schema. The distinction from reply is implied by 'starts a conversation' rather than stated outright, so it stops short of 5.

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?

Usage is only implied: 'starts a conversation' suggests it creates a new thread rather than responding in one. Nothing tells the agent when to prefer reply, send_private_message, or add_offer, and no exclusions are given.

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