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

It adds 'sticky' persistence, the live-seat/external-server context, and the warning that buy/sell/write operations will be refused—useful beyond annotations. It doesn't state undo behavior or what mode changes affect, and 'Read-shaped tools only' is in mild tension with readOnlyHint=false, though not a clear contradiction.

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 purpose is front-loaded, but the description trails into a cut-off sentence ('until the —') and an unrelated server profile/listing URL. It reads like a template mashup rather than a clean, intentional tool description.

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?

The description covers the trigger and follow-up, but it omits the semantics of name/slug, the exact duration of the sticky mode, and how to exit it. For a 3-parameter tool with no output schema, these are material gaps.

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?

Only authCode has a schema description; name and slug are completely undocumented. The tool description never mentions these parameters or how an agent should populate them, leaving a 33%-coverage schema without compensation.

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 first sentence states a specific action ('Enter sticky group-chat mode') with a clear resource, and the trigger phrase differentiates it from data-retrieval siblings like gc_list/gc_history. It doesn't explicitly name sibling alternatives, so it stops short of full differentiation.

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 an explicit trigger ('When the user says I want to chat in the group chat — call this') and a follow-up protocol ('call orbitx_gc_send with every user message until...'). It lacks when-not/alternative guidance, and the duration clause is truncated.

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