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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds that results are public-only and cursor-paginated, plus the note that COMPETITION entries represent external opportunities rather than internal events — useful domain context. It does not disclose result ordering, page sizes, or what the cursor response contains.

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?

A single compact line, front-loaded with purpose followed by filters and then the tool chain. The arrow shorthand is efficient, though the density makes it read like internal notes rather than polished guidance.

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 five-parameter read-only listing tool with no output schema, the definition covers filters and the primary follow-on workflow, and the mention of 'slug' hints at the item identifier. It still leaves the response shape (fields returned, next-cursor handling, default ordering) to inference, which matters more here because there is no output schema.

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%, so the schema already documents all five parameters with examples and enums, making a baseline of 3 appropriate. The description reinforces type/city filtering and cursor pagination but adds no format detail; it also says 'upcoming=true' while the actual parameter is 'upcomingOnly', a small naming imprecision.

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 states a specific verb and resource: browsing ('逛') publicly available activities, filterable by type/city. The word '公开' (public) implicitly separates it from list_my_activities and list_organization_activities, but no sibling is named explicitly, and near-duplicates like list_ecosystem_activities or list_signup_feed remain undistinguished.

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?

It gives concrete usage cues: pass type/city to filter, set upcoming to view future sessions, and use cursor for pagination. The trailing chain 'slug→get_activity→get_signup_activity→submit_signup' is genuinely useful routing to the follow-on tools. What's missing is an explicit when-NOT-to-use or a named alternative among the many list_* activity siblings.

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