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

Discloses login requirement, a 10-60s background read, and crucially that 'returning doesn't mean reading is done' — a non-obvious async behavior. Also states materials are data-only, extracted values must have grounding, and images need user confirmation, adding rich context beyond the lone destructiveHint=false annotation.

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-loads login requirement and the core materials→draft action, then input constraint, then workflow. Dense but every clause carries information; the telegraphic abbreviations cost readability but not correctness.

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?

Covers the async read timing, the one-source-of-input rule, and the downstream workflow — the key things an agent needs for an 8-param tool with no output schema. Minor gap: it doesn't distinguish this from fromActivity reuse semantics in depth, but overall it is complete enough to call correctly.

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% (baseline 3), and the description adds a genuinely new constraint the schema does not encode: give exactly ONE source among text/url/fileRef/fileBase64/imageUrls/fromActivity. Since the schema lists all as independently optional with no oneOf, this mutual-exclusion guidance has real value, plus the ≤700KB and ≤6 image limits are reiterated.

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: importing activity materials to build a new draft, and names the workflow siblings (get_activity_draft → update_activity_draft → publish_activity_draft). The telegraphic phrasing ('活动材料→新草稿') is terse but an agent can distinguish it from add_activity_material and create_organizer_activity.

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?

Explicitly constrains input to exactly one of text/url/fileRef/fileBase64/图片/fromActivity, and lays out the follow-on sequence (get_activity_draft只问nextQuestion→update_activity_draft→publish_activity_draft). This is concrete when-to-use and next-step routing.

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