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

Annotations declare the destructive/idempotent/open-world profile, and the description adds substantial context beyond them: the previewHash-gated execution, re-confirmation on state changes, invitedUserIds preserve-vs-revoke semantics, closed-list effect on exclusive link access, and that notifyInvitees delivery is not guaranteed. This is rich, non-obvious behavioral disclosure.

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?

Permission requirement and preview default are front-loaded, and nearly every clause carries needed information with minimal filler. It is dense and semicolon-packed, which slightly hurts scannability but wastes little.

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 destructive, 8-param mutation tool with no output schema and 0% schema coverage, the description covers the workflow, key parameter semantics, and notification caveats adequately. Remaining gaps are the audience enum meanings and appActivation semantics, which the schema also does not document.

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 0%, so the description must compensate, and it explains the trickiest params: preview (default true), previewHash's role in execution, invitedUserIds (omitted = preserve, empty = revoke), and notifyInvitees (default false, App-only, no delivery guarantee). It leaves audience enum values and appActivation unexplained, so it is strong but not exhaustive.

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+resource: adjusting an organization activity's audience and invitation list (受众、名单), with the two-phase preview/execute nature clear. It distinguishes the operation well but does not explicitly name sibling alternatives to contrast against.

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 gives clear procedural context: default preview=true to inspect impact, then re-invoke with preview=false plus previewHash to execute, and re-confirm if state changed. This is strong guidance on how to use the tool correctly, though it never states when to prefer it over a sibling.

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