List Message Rooms

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds return-shape context (message rooms with participants and last message preview), but it also introduces ambiguity: room_id is described as 'Get messages from a specific room,' while the top-level return is described as a list of message rooms. This makes the exact behavior when room_id is provided unclear.

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 definition is well-structured with an intro, Args section, and Returns section, and the core purpose is front-loaded. It is slightly redundant because the Args list repeats the schema, but it remains compact and easy for an agent to scan.

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 six optional parameters and no output schema, the description does provide a Returns line and documents all arguments. However, the relationship between room_id, message-level output, and room-level output is underspecified, and there is no mention of ordering or how response_format changes the output structure, which leaves meaningful gaps for correct invocation.

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?

The input schema describes all six parameters with defaults and enum values, so schema coverage is 100%. The description's Args list essentially mirrors the schema without adding constraints, relationships, or practical usage nuance, so the baseline of 3 is appropriate.

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 a read-only list/view operation over Upwork message conversations and message rooms, naming the resource and even the return shape. It does not explicitly disambiguate from siblings like upwork_send_message, but the viewing intent is obvious from the wording.

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 is the tool to use when you want to see your message rooms or conversations, but it never explicitly says when to use it versus alternatives such as upwork_send_message. There is no exclusion or 'when not to use' guidance, so usage is mostly inferable rather than stated.

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