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

With only destructiveHint=false in annotations, the description carries rich behavioral context: admin permission required, org admin is notified, hard rate limits, temporary/non-transferable authorization scope (不跨活动/申请人/重入), and no audience expansion, invitation, or contact disclosure. This is exactly the extra context that annotations do not provide.

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?

Front-loaded with the permission tag and core purpose, and every clause carries operational meaning (limits, preview flow, scope boundaries). It is dense and clause-heavy, but not bloated; minor tightening would make it easier to parse.

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 mutation tool with no output schema and minimal annotations, the description covers permissions, rate limits, confirmation protocol, and scope boundaries an agent needs to invoke it correctly. Nothing essential is 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 coverage is 0%, and the description compensates well for the key flow: preview defaults to true, and confirmation reuses the same parameters plus a previewHash with preview=false, with any change forcing re-confirmation. It also ties the ≤20 batch limit to userIds. activityRef and note are left to the schema, which is a minor 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 specific verb (申请/request) plus resource (本场指定云成员的限期联系授权) and scope (single activity's designated cloud members). Negations like 不邀请 and 不出联系方式 clearly separate it from invite_activity_cloud_member_manually and review_activity_cloud_contacts.

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 the precondition (需管理权限·通知组织管理者), batching rules (每批≤20人、每日20次；大名单分批确认), and the preview-then-confirm flow. It does not name sibling alternatives outright, so an agent must infer that invitation or review actions belong to other tools.

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