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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds 'live' and 'active communities table' context, but does not disclose behaviors like data freshness windows, pagination, or whether an authCode is required, though the authCode schema description partially covers that.

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 with no filler. The core action and resource are front-loaded, and the parenthetical about the active communities table adds useful context without bloat.

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?

This is a simple read-only list tool with two optional parameters, and annotations cover its safety profile. However, the description omits limit semantics and does not describe the returned community data, and there is no output schema to compensate. It is adequate but has clear 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?

Schema description coverage is 50%: authCode is richly explained in the schema, but the limit parameter has only a type and default. The description does not compensate by explaining limit semantics, allowable ranges, or pagination behavior, so a key parameter remains under-documented.

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 uses a specific verb ('List') and a specific resource ('live OrbitX communities') and identifies the underlying endpoint (/communities) and table ('active communities table'). It is clear enough to distinguish from many sibling tools, though it does not explicitly contrast with similar list tools like orbitx_social_feed or gc_list.

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 gives no guidance on when to use this tool versus alternatives such as orbitx__orbitx_social_feed, orbitx__orbitx_gc_list, or other community-related tools. It does not state exclusions, prerequisites, or context in which another tool should be preferred.

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