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

Annotations only declare readOnlyHint=true, and the description adds a lot beyond that: server-side authorization recheck, hidden/test-record isolation, a fixed page size of 50 with nextCursor paging, total returned only on the first page, phone numbers never returned, and the meaning of isCloud=true (user hasn't onboarded, so no chat or task assignment). This is exactly the behavioral context annotations cannot carry.

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 prerequisite is front-loaded, then the operation, then pagination, then data-masking caveats. The dense clauses each carry information, though the isCloud and phone-number notes read as a run-on tail that could be split for scannability.

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 read-only list tool with no output schema and no schema descriptions, the description covers auth, pagination, isolation of hidden/test records, data masking, and a key field semantic (isCloud). It omits result ordering and which fields the roster returns, which would matter for composing follow-up actions.

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 0%, so the description must carry the burden, and it explains that q is a nickname search over the entire roster rather than only the current page, and that cursor drives paging. It says nothing about the allianceId/organizationId relationship or constraints; it only implies the pair through 'alliance identity and directory authorization'. Partial compensation, but not full.

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 names a specific verb and resource: it reads an alliance-subordinate organization's member roster that the org has opened to the alliance. The scope is narrow enough that an agent won't confuse it with list_organization_members or list_chain_group_members. However, it never names those siblings, so the agent must infer the difference from scope alone.

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 states a prerequisite (login required, server-side recheck of alliance identity and directory authorization) and implies the context (roster opened to the alliance). It gives no explicit when-not to use it and doesn't route to a sibling such as list_organization_members; usage must be inferred from scope.

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