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

Annotations only declare readOnlyHint=true; the description adds substantial non-derived context: nothing is published, times are suggested values, offline venue is left blank and must not be treated as confirmed, closed activities use INVITEES, and cloud/non-native-app users are invited separately after publishing. This is exactly the behavior an agent needs beyond the annotation, and it is consistent with readOnlyHint (a pre-fill/derive operation with no side effects).

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 critical pre-fill/do-not-publish constraint, then behavior, then the downstream handoff — a sensible order. The text is dense with internal jargon (PAIR/GROUP, INVITEES, 云用户) and a stray '登录;' prefix that does not earn its place, but there is little true redundancy.

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?

With no output schema, the description does the work of sketching the return: an activity object usable as input to create_organization_proposal_activity, with suggested times, unfilled venue, and an invitedUserIds list containing only real people. The main residual gap is the unexplained guestUserIds input, which matters for a tool an agent must parameterize correctly.

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?

At 50% schema coverage the description carries partial burden: it explains excludeUserIds including the 100-person cap that matches maxItems. However guestUserIds (max 30) is never explained, and the description instead references invitedUserIds, which is not an input parameter of this tool, creating mild ambiguity about what can actually be passed in.

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+resource: convert a PAIR/GROUP proposal into an activity form pre-fill. The bracketed 【只预填，不发布】 immediately scopes it as a draft-generation step and it names the downstream sibling create_organization_proposal_activity, so an agent can distinguish it from publishing/creation tools 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 clear when-to-use context (pre-fill only, never publish) and an explicit alternative/next step (create_organization_proposal_activity as the publish path, after confirming body/time/location and invitee list). It does not address when to prefer this over other draft-producing siblings such as draft_organization_match_activity, so it stops just short of a full when/when-not treatment.

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