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

Annotations cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds genuinely new context: the login requirement and the caveat that reading archived items does not restore or modify history. This meaningfully reduces the risk of an agent assuming a side effect.

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 login requirement, then return contents, defaults, routing, and a caveat in short dense clauses. Every clause carries distinct information with zero filler, and the ordering puts the prerequisite first.

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 list tool with no output schema, it lists returned fields, default filter state, routing, and the archive caveat. The only minor omission is pagination/result-size behavior, which is not addressed.

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 both params (baseline 3). The description goes slightly beyond by stating the default archived behavior and the priority nuance that q filters by title first ('q先按标题筛'), clarifying ordering of the filters.

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 (列/list) and a precisely scoped resource: activities the caller can manage, which separates it from signup-based lists like list_my_signups. It also enumerates the return content (signup totals, pending count, role, signup config). However, it never explicitly distinguishes itself from close siblings such as list_activities or list_my_activity_history.

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 explicit conditional routing: slug→get_organizer_activity and pendingCount>0→list_signup_submissions, plus the default (non-archived) vs archived=true (canceled/delisted) filter behavior. This is strong when/when-not guidance. The gap is that it does not clarify when to prefer this tool over other list_* activity siblings.

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