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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description's read-shaped/refuses-writes note aligns with them. It adds only minor context ('their data comes back as it is') and does not disclose auth details, rate limits, or result-shaping behavior beyond what annotations provide.

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 core instruction is front-loaded and the trigger example is useful, but the description includes extra server/listing context (Orbitx's MCP server, a live seat on The Wall, and a registry URL) that does not help invoke the tool. It is not overlong, but it does not earn every sentence.

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-parameter, read-only list tool, the description covers the main call pattern and return expectation ('read the names back'). However, it lacks clarity about the limit parameter and does not mention the authCode requirement, leaving some setup ambiguity despite the schema's coverage.

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 adds no meaning for either parameter; only authCode gets a description in the schema, while limit is left to its default value. With 50% schema coverage and no compensating prose, an agent cannot tell whether limit truncates the list or how authCode should be supplied.

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 begins with a specific verb+resource ('List open group chats') and adds an explicit trigger phrase for when to call it. It does not explicitly contrast it with sibling tools such as orbitx_gc_focus or orbitx_gc_history, so it falls short of the top score.

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 gives clear user-intent guidance ('when the user says hey any group chats / any group chats, call this and read the names back'). It does not mention alternatives or when not to use this tool, which keeps it at 4 rather than 5.

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