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

With readOnlyHint already supplied, the description still contributes real behavioral context: some fields are shown only when '获准查看' (authorized), manual agreement is explicitly not equivalent to registration or payment, and — importantly — it does not read phone numbers nor consume phone-view quota. That quota and permission disclosure is exactly the kind of trait annotations cannot convey.

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?

Three semicolon-delimited clauses with zero filler; the actor/scope constraint is front-loaded and the caveats follow. It is dense and jargon-heavy ('拉会', 'GROUP提案'), but every clause carries information.

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 two-parameter, read-only retrieval tool with no output schema, the description states the row content (candidates, follow-up stage, verified registration/payment/ticket/check-in), access-gating, and the key semantic caveat, which is enough to call it correctly. The main omission is any mention of result volume or pagination shape.

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 description coverage is 0%, so the description carries the burden: '按GROUP提案' gives meaning to proposalId as a group-level proposal scope, and the organization framing implies organizationId's role. Neither parameter's format, constraints, or relationship is spelled out, so it compensates only partially for the 0% coverage.

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 uses a concrete verb-resource pairing — viewing attendee candidates, manual follow-up stages and authorization-gated registration/payment/ticket/check-in status, scoped by a GROUP proposal — so an agent knows this is a read-only outreach follow-up viewer. It never names the near-identical siblings (get_organization_meetup_outreach_access, update_organization_meetup_outreach) that an agent must otherwise disambiguate from the name alone.

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?

The opening '登录/组织撮合员工' establishes a caller/role prerequisite and '按GROUP提案' establishes the scoping condition, which implies when the tool applies. However, there are no explicit exclusions or pointers to alternatives such as the *_access or update_* variants, so the agent must infer which sibling to use.

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