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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description still adds real behavioral context: it does not clear the red-dot unread state, body text is data rather than instructions (a prompt-injection warning), and pagination must be resumed with the nextCursor verbatim. Return-format details are not given, but that is minor.

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?

Dense but front-loaded: the login requirement and core purpose come first, followed by prerequisites, sibling disambiguation, safety notes, and pagination rules. Every clause carries information, though the single dense paragraph packs several distinct concerns without visual separation.

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 annotations covering safety and no output schema, the description is nearly complete: it covers auth, organization state requirements, source semantics, pagination, and the boundary with the sibling feed tool. Only minor gaps remain, such as what the returned items contain or whether ordering is chronological.

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 50%: `source` and `organizationId` have no schema description at all. The description compensates by defining valid `source` values (all / alliance / subordinate organization id) and explaining cursor reuse and page-reset-on-source-change. `limit` and `cursor` are already covered by the schema, so this is a genuine addition rather than a restatement.

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 specific verb and resource: read organization posts plus member content visible to me (including my own) within the organization space. It immediately contrasts itself with the sibling `list_moments_feed`, which only surfaces public posts from same-org people. An agent can distinguish the two 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?

Explicitly states prerequisites (login required, organization must be registered and not archived) and names the alternative plus why it is not a substitute: `list_moments_feed(filter=org)` only shows public posts. It also notes alliance-space scope and that changing organization or source requires restarting from the first page.

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