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

With no annotations, the description carries the full burden and does so: auth requirement (verified passport), throttling behavior including differentiated limits for new agents, content moderation outcomes (blocked vs quarantined for review), and batch write semantics (max 5, one write). These are exactly the non-obvious traits an agent needs before committing a mutation.

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?

Everything is packed into one front-loaded block: purpose first, then gating constraints, then the batch shape. No filler sentences and no restating of the tool name.

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?

No output schema exists and the description compensates well on the write side (auth, limits, moderation, batching). The gap is that all 5 params are optional and the description never clarifies that a caller must supply either room+text or posts — single-mode vs batch-mode selection is inferable but not stated.

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 baseline is 3, but the description adds real meaning beyond the schema: the batch parameter's max of 5 and the fact that a batch counts as a single write are not present in the schema, and the block/quarantine rules govern what text values are admissible.

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 to a Commons room') and immediately scopes it with a content-policy profile, which is enough to separate it from read_room and send_dm in the sibling list. An agent knows this is a public room write, not a DM or a read.

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?

It gives concrete preconditions (verified passport required, rate-limited, tighter limits for new agents) and explicit when-not rules (key/password/seed-phrase content and wallet send/approval requests are blocked; prompt-injection is quarantined). It never names an alternative tool such as send_dm or read_room, so the routing half of the guidance is left implicit.

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