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

Annotations only declare destructiveHint=false, so the description carries most of the burden and does well: it discloses that publication is public and immediate with after-the-fact review, that user confirmation is mandatory, and that 409 compose_version_stale requires re-reading and re-displaying rather than retrying the stale version. It does not say what a successful publish returns or whether an already-live activity can be retracted.

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/public-publish tags, then prerequisites, then error handling, so the most decision-relevant information comes first. The telegraphic arrow notation and compressed clauses make it harder to parse than plain prose, but no sentence is filler.

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 2-parameter mutation with no output schema, the description covers preconditions, side effects (public, live, post-moderated), the 409/422 failure modes, and the eligibility escalation path. The main remaining gap is what the agent receives on success (activity id or link) so it can report back to the user.

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% and the schema already explains the optimistic-lock semantics of version and where composeId comes from. The description only reinforces the workflow provenance ("传刚读version"), which adds little beyond the schema text. Baseline 3 is appropriate here.

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 (publish), the resource (activity draft), and the exact effect (goes live immediately, moderated afterwards). It is clearly distinguishable from update_activity_draft, ensure_activity_live, and import_activity_draft in the sibling list.

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?

The description prescribes the ordering with siblings: read via get_activity_draft, pass the just-read version here, then render_activity_letter if an invitation letter is needed. It also states a hard precondition (must have user confirmation) and an exclusion (if eligibility is insufficient, the agent must NOT fill in organizer details, the user completes it in the App).

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