tomo_create_room

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

With no annotations, the description carries the full burden. It states the tool creates a room but does not disclose what happens if the room already exists, if there are side effects, or what default values apply for unspecified parameters. It does not state whether this is a write or read operation, or if authentication is needed. However, the 'Create' verb in the description is consistent with a mutation, so there is no contradiction.

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, concise sentence that efficiently conveys the tool's purpose with relevant examples, containing no superfluous words.

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?

The description is somewhat complete for creating a room given the input schema, but it lacks details on return values (no output schema, so this is a gap) and edge cases (e.g., behavior with duplicate names). The sibling tools list suggests related tools exist, but the description does not reference them for further context.

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 coverage is 100%, providing descriptions for all 3 parameters. The description adds context by listing examples of 'type' values (e.g., 'camera-stream-server'), which is not in the schema. However, it does not explain the 'source' parameter in detail, which could be ambiguous (device configuration or identifier).

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 tool creates a streaming room, with specific examples of what can be streamed (camera, desktop, plugin). It uses a specific verb 'create' and resource 'streaming room', and effectively distinguishes itself from siblings like tomo_list_rooms (list) or tomo_delete_room (delete).

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?

The description implies this tool is used to create a streaming room, but it does not explicitly state when to use this tool versus alternatives like tomo_control_room (presumably for controlling existing rooms) or tomo_list_stream_servers (for listing available types). There is no guidance on required prerequisites (e.g., needing a stream server type).

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