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

With readOnlyHint=true already covering the safety profile, the description adds real behavioral context: a login prerequisite, a role-based scoping rule (ordinary staff see only the service-layer-allowed subset), and an explicit data-authority constraint that relationship/governance classifications must not be inferred ('仅按服务端下发，不推断'). Return-shape detail (no pagination, no size limits) is absent, so not a 5.

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?

Login gate and reader scope are front-loaded, then the returned sections, then the caution and the sibling pointer — a sensible order with no filler sentences. It is dense, semicolon-joined prose that takes a second read, which keeps it from a 5.

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 one-parameter, read-only tool with no output schema, the enumerated return sections substitute well for schema documentation, and the authorization caveat prevents misuse. The gaps are minor: no indication how to obtain a valid allianceId and no note on result size or empty-state behavior.

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?

The single parameter allianceId has 0% schema description coverage and the description never explains it — no format, no hint that it comes from search_alliances, no statement about what happens for a non-member. The phrase '联盟在册身份' only weakly implies the ID must reference an alliance the caller belongs to, which is not enough to compensate for the coverage gap.

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?

States a concrete verb+resource ('联盟在册身份读工作台') and enumerates exactly what the read returns: capabilities, subordinate organizations, actual authorizations, pending applications/invitations, and staff. It explicitly separates itself from the sibling get_alliance ('公开页用 get_alliance'), so an agent can pick between the two without opening a 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?

Gives the audience condition ('联盟在册身份', requires login) and the permission ceiling for ordinary employees ('普通员工只读服务层允许范围'), plus an explicit alternative for the public case ('公开页用 get_alliance'). There is no further guidance on failure modes or what to do if the caller is not a registered member, which keeps it at 4 rather than 5.

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