Connect Matrix room bus

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description only needs to add context beyond safety. It does add some value by mentioning 'sanitized room events' and 'token/encryption safety notes,' which hint at data hygiene and security considerations. However, it does not disclose the actual side effects of creation, such as whether external systems are contacted, whether existing room data is modified, or what the scaffold's runtime behavior will be. The description adds moderate context but is not rich.

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?

The description is a single sentence that packs in the key components without redundancy. It is front-loaded with the main action and resource, and then lists included features. It could be slightly clearer with breaking into two sentences, but it is efficient and free of 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?

With 10 parameters, no output schema, and low schema description coverage, the description carries a heavy burden that it does not fulfill. It omits details about where the scaffold is created (beyond the parent_path parameter), what the adapter source implies, how the approval policy works, and what the token/encryption safety notes actually do. The description is a high-level summary but leaves many operational questions unanswered for an agent attempting to invoke it correctly.

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 only 20%, with only 'name' and 'parent_path' having descriptions. The tool description does not map its mentioned components (sanitized events, reaction maps, approval policy, etc.) to specific parameters like room_alias, adapter_mode, reaction_count, room_event_count, or approval_required. With 10 parameters and minimal schema descriptions, the description should compensate by explaining parameter roles; it fails to do so, leaving most parameters semantically opaque.

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 uses a clear verb ('Create') and identifies the resource ('a Matrix room scaffold'), and further specifies the scaffold includes sanitized room events, reaction maps, approval policy, adapter source, and token/encryption safety notes. This makes the tool's purpose fairly specific and distinct from generic connect/create tools, though it doesn't explicitly differentiate from sibling tools that also create scaffolds or buses.

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?

No guidance is provided on when to use this tool versus alternatives. There are many sibling tools with similar names (e.g., connect_websocket_control_bus, create_blacktrax_tracking_bus, connect_mqtt_iot_bus), but the description does not mention any of these or specify conditions for selecting this Matrix-specific tool. No exclusions or alternative scenarios are given.

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