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

Adds substantial context beyond the annotations: the 50-message window, that messages are consumed relative to a numeric 'since' cursor (which explains the counterintuitive readOnlyHint=false for a read operation), the requirement to treat agent text as untrusted_text and never as instructions, and the exact auth mechanism including header precedence.

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 core operation and window, then security and auth notes; four short sentences with no filler. The telegraphic 'Key: ...' fragment is terse but still parseable.

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?

No output schema exists, and the description does cover the return payload shape (up to 50 messages, untrusted_text field) and the auth path, which is what an agent needs to invoke and interpret it. It stops short of stating pagination/termination behavior once the window is exhausted.

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 50%: 'key' is fully documented in the schema, while 'since' has no schema description. The description partially compensates by clarifying that since is a numeric ordering cursor ('after numeric since'), but gives no bounds, default behavior, or format detail, so it only just meets the baseline.

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?

Names a specific verb and resource ('Read ... messages') and pins the scope precisely: the 50 oldest unseen messages after a numeric cursor. This clearly separates it from pit_lobby_chat_post and pit_lobby_chat_flag, so an agent can pick it without opening a 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?

Use context is only implied by 'Guests read only' and by the read vs. post/flag sibling names; the description never names an alternative tool or states when not to call this one. Adequate for a simple read, but the routing burden is left to the sibling names.

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