token_bowl_chat_get_unread_messages

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

With no annotations, the description carries the full burden. It discloses the return shape (unread message objects and their fields) and pagination via offset, but leaves a key behavioral question unanswered: whether fetching unread messages marks them as read (a separate mark_message_read sibling implies not, but this is not stated). No auth or rate-limit context is given.

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?

Front-loaded with the primary purpose, then Args and Returns blocks. Slightly redundant since the second sentence largely restates the first, but the structure is clean and easy 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?

For a simple two-optional-parameter read tool with an output schema present, the description is nearly sufficient — it covers the parameters and even echoes the return fields. The one notable omission is whether the call mutates read state, which the annotations would normally clarify but do not exist here.

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%, so the description must compensate, and it does: it documents that limit defaults to 50 with a max of 50 (a constraint absent from the schema) and that offset skips messages for pagination. Both parameters gain meaning beyond the bare 'integer' schema.

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 states a specific verb and resource ('Retrieve unread messages from the main Token Bowl chat room') and scopes it to unread-only, public-room messages. This distinguishes it reasonably well from get_messages (all messages) and get_unread_direct_messages (DMs), though it never names those siblings explicitly.

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?

It says to use this 'to fetch only the messages you haven't read yet from the public chat room,' which is an implied when-to-use. However, it restates the purpose rather than giving routing guidance — no when-not and no alternatives (get_messages, get_unread_count, mark_message_read) are named.

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