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

Annotations already declare readOnlyHint=true, so '只读' merely restates structured data. The description does add the authorization requirement (login/organizer), which is genuinely useful and not in the annotations. It says nothing about pagination, result size, or what a non-organizer caller sees, so the added behavioral context is thin but non-zero.

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 telegraphic clauses with the permission model and read-only nature front-loaded, then the routing hints. No wasted text, though the semicolon-separated fragments are terse enough to read as notes rather than prose.

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 one-parameter read tool with no output schema, the description covers access control and scope but not what the response contains (a list of banned users? upload records?) or its size/shape. It is adequate to call correctly but leaves the agent guessing about the result.

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 one parameter at 0% schema description coverage, the description must compensate. '本场' implies activityRef identifies the event being inspected, but it gives no format, lookup source, or validation hint beyond what the schema's minLength/maxLength already convey.

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 names the resource and its scope: the read-only '禁传名单' (blocked-upload list) for this specific activity ('本场'). An agent can tell it retrieves moderation state rather than activity content, though the verb is implicit and the returned entity (blocked uploaders) is only inferred from the title.

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 supplies a real prerequisite ('登录/主办方' – must be logged in and be the organizer) and redirects two adjacent tasks to list_activity_materials and get_activity_material_download. However, those are different operations, not true alternatives to this tool; the actual write counterpart, moderate_activity_album_uploader, is never mentioned, so the when-to-use-this-vs-modify decision is left to inference.

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