Connect Matrix room bus

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

Annotations (readOnlyHint=false, destructiveHint=false) align with the 'Create' action, and the description adds useful detail about what the scaffold includes (e.g., token/encryption safety notes). However, it does not disclose side effects, required permissions, or network interactions beyond the basic create action. The annotations reduce the burden, so a baseline 3 is appropriate.

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, front-loaded with the primary verb and resource, and lists the key components without rambling. Every word contributes to clarity.

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 tool with 10 parameters, no required fields, and no output schema, the description is too brief. It does not explain the purpose of the 'bus', the meaning of adapter modes, the expected return value, or the context in which a Matrix room scaffold is needed. The annotation openWorldHint=true implies flexibility, but the description leaves too much to inference.

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% (2 of 10 parameters have descriptions), and the tool description adds no parameter information. It does not compensate for the low coverage, leaving many parameters (reaction_count, adapter_mode, approval_required, etc.) without semantic explanation beyond their names.

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 clearly states the action: 'Create a Matrix room scaffold' and enumerates specific components included (sanitized room events, reaction maps, approval policy, adapter source, token/encryption safety notes). This verb-resource pairing is specific and distinguishes it from many sibling connect_* tools.

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. The description is purely declarative and does not mention exclusions, prerequisites, or alternative tool recommendations.

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