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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 'Read' is consistent but adds no extra behavioral context. It does not disclose what happens if no chat is focused, whether a name or slug is required, or any side effects beyond the read operation. The description carries little burden given annotations, but it still fails to add useful context.

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 sentence, front-loaded with the action, and has no unnecessary words. However, it is too terse; it omits essential details that could be added concisely, so it is under-specified rather than appropriately concise.

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?

Given 4 parameters (none required), no output schema, and no parameter descriptions in the tool description, the description is incomplete. It does not explain how to select a chat (name vs slug), what the limit does, what 'focused' means, or what the response format is. An agent cannot reliably call this tool correctly based on the description alone.

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 description provides zero information about the parameters name, slug, or limit. With only 25% schema description coverage (authCode has a detailed description), the description does not compensate at all. Agents cannot determine how to specify a chat or what limit controls, making parameter usage ambiguous.

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 action ('Read') and a clear resource ('recent messages in a group chat'), with a mention of an alternative ('or the focused one'). It is clear enough to distinguish from sibling tools like orbitx_gc_list (which lists chats, not messages), but it does not explicitly name or exclude any sibling.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how the 'focused' chat is set. The single hint 'or the focused one' implies a focus concept but is not elaborated, leaving the agent to infer usage context.

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