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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that: required permission (publishActivities), a hard result cap of 500, the visibility scoping rule, and the exact field set returned. Pagination and filtering behavior remain undisclosed.

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?

Two compact sentences, front-loaded with the auth/permission prerequisite and result cap, followed by the draft-workflow pointer. Dense but every clause carries information; minimal waste.

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 read-only listing tool with annotations and no output schema, the description covers the essentials: permission gate, result limit, scope rule, and returned fields. Only pagination and how member visibility affects the candidate set are left implicit.

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?

With schema coverage at 0% and one parameter, the description carries the burden but never explains organizationId's meaning or format. It only frames the org context implicitly via 'organization activity', so it adds little parameter-level semantics beyond the obvious self-describing ID.

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: lists up to 500 invitable candidates for an organization activity, scoped by member visibility, returning identity/nickname/avatar. This is understandable on its own, but it never names or contrasts with near-siblings like list_organization_activity_pick_candidates or list_guest_invitation_candidates, leaving an agent to infer the distinction.

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 preconditions (【需登录、publishActivities】) and contextual workflow (import_activity_draft → update_activity_draft → publish_activity_draft, set the roster in the draft org). However, it does not state when to prefer this over the other candidate-listing tools, so usage is only implied.

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