matrix_create_room

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

No annotations are supplied, so the description carries the full burden. It does disclose that the operation is dry_run-able and that preset controls room visibility (public vs private), which is genuine behavioral context, but it says nothing about required permissions, whether invites notify users, or what side effects occur on creation.

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 short sentences with the core action front-loaded and zero filler; the preset list and id format are the two facts an agent most needs. Slightly terse at the cost of the undocumented parameters, but structurally sound.

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?

An output schema exists, so return values need not be explained, and the description covers the highest-risk parameters (preset, invites, dry run). Still, for a 7-parameter mutation tool with no annotations and 0% schema coverage, four parameters and all permission semantics are left 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 0% across 7 parameters, so the description must compensate. It covers preset (values plus default) and invite_user_ids (required @user:server.tld format), and touches dry_run, but leaves name, topic, tenant, and is_direct entirely undocumented in both places.

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 ('Create a new Matrix room') that no sibling shares — every sibling is a read/send/list/invite tool, so the create action is unambiguous. An agent can identify the tool without opening the schema.

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 implied by the verb and by the absence of any sibling that creates rooms, and the preset enumeration hints at the intended privacy modes. However there is no explicit when-to-use/when-not guidance and no mention of prerequisites such as being joined to a homeserver or tenant scoping.

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