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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new context beyond annotations: the login requirement and organizer-only authorization. It does not describe return contents or pagination, which keeps it out of 5 territory.

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 tight sentences with zero waste: a bracketed prerequisite marker, the core purpose, then sibling routing. Front-loaded and every clause earns its place.

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 single-parameter read-only tool with no output schema, the description covers authorization, purpose, and sibling routing well. The remaining gap is that it does not tell the agent what the ban list contains (identities, timestamps) or how activityRef is obtained, which leaves some ambiguity.

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% and the single required activityRef parameter is undocumented anywhere. The description implies activity scoping via 本场 (this event), but adds no format, source, or meaning for activityRef, so it only marginally compensates for the schema gap.

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: reading the read-only ban list for this activity's album uploads (只读本场禁传名单). It names two adjacent siblings (list_activity_materials, get_activity_material_download) to disambiguate, but never names the closest sibling moderate_activity_album_uploader, its write counterpart, so the differentiation is partial rather than complete.

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?

Gives clear context (organizer, login required) and explicitly routes the agent to alternatives for the adjacent material/download tasks. It stops short of stating when-not to use it (e.g. that banning is done via moderate_activity_album_uploader), so it lacks explicit exclusions.

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