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

Goes well beyond the single destructiveHint:false annotation: it discloses the management-permission requirement, that the whole form is replaced, that series_default clears overrides and affects inheriting sessions, the version binding, that no invitations are sent, and the default-preview/confirm-with-previewHash safety flow. That is rich behavioral context an agent needs before calling.

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?

Permission requirement and replacement action are front-loaded, then scope, then workflow. It is dense and semicolon-packed but nearly every clause carries operational meaning; slightly run-on but efficient.

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 complex, nested-config mutation with no output schema, it covers permission, scope effects, safety flow, and side-effect (no invitations). The main gap is detail on config field contents, but the schema supplies that structure, so the description is adequately complete.

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 0%, so the description must carry the load, and it does for the tricky parts: it explains scope=series_default semantics, that preview defaults to true, and the previewHash confirmation mechanism (same params + previewHash, preview=false). It adds little about the nested config.fields structure, which the schema covers structurally.

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 (整份替换/full replacement) and resource (活动嘉宾资料表/guest profile form), and the replacement semantics distinguish it from get_activity_guest_collection and update_my_guest_profile. It does not name siblings explicitly, so 4 rather than 5.

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?

Clearly explains the scope=series_default vs activity choice (series_default changes the series default and clears this session's override, affecting inheriting sessions) and lays out the preview→confirm workflow. It gives strong context but does not explicitly name alternative tools or exclusion conditions.

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