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

Annotations only declare destructiveHint=false, so the description carries real weight and delivers: auth + permission requirements, ~30s model latency, quota consumption, PROFILE fallback behavior, and confirmation that no create/invite side effects occur. A 4 rather than 5 because 'PROFILE为回退' is cryptic about what the fallback actually does.

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?

Extremely compact and front-loads the login/permission requirement, then side-effect scope, then the chain. Every clause carries information, though the bracketed shorthand and mixed jargon slightly hurt readability.

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 2-param drafting tool with no output schema, the description covers auth, cost, latency, side-effect boundary, fallback, and the downstream chain to create_organizer_activity. Only the nature of the generated draft copy and the PROFILE fallback remain underspecified.

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 100% and both parameters (organizationId, pairId) are documented in-schema, including the important warning that pairId is userId:userId not a proposal id. The description adds nothing beyond this, so the baseline 3 applies.

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 (draft an organization match activity) and immediately scopes it: '仅起草不创建/邀请' (only drafts, does not create/invite), which distinguishes it from create_organizer_activity. However, the phrasing is compressed into bracketed tags, so some purpose nuance (e.g. what 'match activity' produces) must be inferred.

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?

Provides clear preconditions (requires login, matchmaking management and publishing permissions) and names the follow-up alternative create_organizer_activity in the '组合链'. It stops short of explicit when-not-to-use guidance or naming sibling draft/read tools like get_organization_proposal_activity_draft.

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