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

The description goes well beyond the annotations (which only cover readOnly/idempotent/openWorld safety): it discloses login requirement, server-side revalidation of alliance identity and directory authorization, hidden/test isolation, 50-per-page pagination with cursor, total only on page one, and – critically for downstream behavior – that isCloud=true people haven't used the App and cannot be chatted or assigned tasks, and that phone numbers are never returned. That last point is important behavioural context because the schema cannot express it. It doesn't contradict the readOnly hint.

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 packs a lot of relevant information efficiently. It is front-loaded with the access requirement (【需要登录】), then the resource, then pagination and behavioral caveats. Dense but every clause carries distinct information; no wasted sentences.

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, the definition supplies exactly the missing pieces an agent needs: auth/login requirement, the authorization model, pagination contract, result-set quirks (isCloud), and a data-hygiene guarantee (no phone numbers). Nothing important to invoking it correctly appears to be missing.

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 should compensate, and it partially does: '按昵称搜索' clarifies that q is a nickname search, '每页 50，nextCursor 翻页' documents cursor semantics, and the required ids are implicit from the title (alliance + sub-organization). However allianceId/organizationId are not explained in the description and there is no mention of the maxLength constraints on q and cursor, so the documentation of parameters remains incomplete.

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 states a specific verb (read) and resource (a member roster that an alliance member organization shares with the alliance), and distinguishes it from the sibling list_organization_members by framing the roster as 'opened to the alliance' and describing it as a directory. An agent could pick this tool over its siblings without opening either schema.

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 establishes the context clearly: reading an alliance-scoped roster, requiring login and server-side checks of alliance identity plus directory authorization. It does not name an explicit alternative (e.g. list_organization_members for the org's own roster), so there is no when-not guidance, but the scoping conditions are specific and actionable.

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