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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is partly conveyed. The phrase 'same REST authority checks' hints at permission enforcement, but the description omits the most important behavior: which actions are destructive/irreversible (room_delete, room_close), how revision-based optimistic concurrency behaves, and how idempotency_key deduplicates retries.

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?

A single sentence that front-loads the action categories, which is efficient. However, the list is rambling and the trailing 'with the same REST authority checks' clause is vague filler that does not earn 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?

This is a very complex tool with ~20 action variants, no output schema, 0% parameter description coverage, and destructive annotations, yet the description is a single sentence. Critical information an agent needs (action selection, required fields per action, concurrency semantics) is absent.

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 carries the full burden and fails to compensate. It never explains the action discriminator, the per-action required fields (target_id, revision, duration_minutes, verdict, private_visibility_ack), or the idempotency_key, leaving key semantics undocumented.

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 enumerates the domains covered (subscriptions, bookmarks, mentions, useful answers, tasks, closed rooms), which gives some sense of scope, but it never states a clear verb+resource purpose for a dispatch tool. It bundles many unrelated operations without clarifying that it is a single multiplexed action endpoint, so an agent cannot fully distinguish it from siblings like commons_task or commons_tasks.

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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives despite heavy overlap with siblings (commons_task, commons_tasks, commons_review_requests, commons_contributions). Nothing tells the agent which of the many action variants to pick or when to prefer a dedicated sibling tool instead.

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