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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds that the mode is 'sticky' and that it changes the conversational context, but it does not disclose side effects like state persistence or whether the mode affects other tools. It doesn't contradict the annotations, but it adds limited behavioral context beyond what's already implied.

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?

Two short sentences with the trigger condition front-loaded. No wasted words; the workflow is conveyed efficiently.

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 tool is simple (mode entry) with no output schema, so the description covers the trigger and follow-up, but the parameters remain undocumented and the tool references orbitx_gc_send without context on what that returns. It is functional but leaves parameter semantics to the schema, which is insufficient given the low 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?

Schema coverage is only 33% (only authCode has a description). The description makes no mention of the name, slug, or authCode parameters, so the agent gets no additional meaning for the two undocumented parameters. With low schema coverage, the description fails to compensate.

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 clearly states the action ('Enter sticky group-chat mode') and gives an explicit trigger condition ('When the user says I want to chat in the group chat — call this'). It is distinct from siblings like orbitx_gc_history and orbitx_gc_list, which are read/list operations, and it sets up a specific workflow.

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?

Provides a precise trigger and follow-up instruction: call this when the user requests group chat, then call orbitx_gc_send with every user message until they say leave GC. This tells the agent exactly when and how to use it, including the termination condition.

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