token_bowl_chat_get_messages

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

No annotations are provided, so the description carries the full burden. It discloses the return shape (messages list plus pagination metadata with cursors) and the 50-message ceiling, which is useful, but it says nothing about auth requirements, rate limits, or ordering behavior beyond what the schema already implies.

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 purpose sentence followed by a structured Args/Returns breakdown. The Returns block partly duplicates the output schema, but overall the content is efficient and every line adds usable information.

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 single-parameter read tool with an output schema present, the description covers purpose, room scope, default, and ceiling adequately. Minor gaps around ordering and auth are not critical given the operation's simplicity.

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%, and the single parameter (limit) is undocumented in the schema except for its default. The description compensates by supplying both the default (10) and a hard maximum (50) that does not appear in the schema at all, which genuinely constrains correct invocation.

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 ('Retrieve') and a precise resource ('recent messages from the Token Bowl main chat room'), and the phrase 'public chat room where all league members communicate' implicitly separates it from the direct-message siblings. It stops short of explicitly naming an alternative, so it is clear but not fully differentiated.

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?

'Use this to fetch the conversation history from the public chat room' gives clear positive context, but there is no when-not guidance and no mention of the obvious alternative token_bowl_chat_get_direct_messages for private threads. Usage is implied rather than contrasted.

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