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

The description discloses a login requirement, a first-open prefill side effect (not pure read-only), and a privacy constraint that contact original text is never returned, only hasContact + contactMode. These go beyond the annotations and are fully consistent with readOnlyHint=false.

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?

The description is compact and structured with labeled sections: login/when-to-use, combination chain, and data-scope policy. Each sentence adds distinct operational value with no filler or redundancy.

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 tool with no output schema, the description covers when, prerequisites, the prefill side effect, and key returned concepts (missing fields, photo state, completeness, contact flags). It is slightly light on the full return payload, but the essential operational context is present.

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 compensate for parameter meaning. It explains that guestId is obtained from list_my_invitations / respond_activity_invitation and feeds into update_my_guest_profile, which provides useful provenance for the single required parameter.

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 explicitly states the tool reads current guest-profile values before editing, including missing items, photo cutout status, and completeness. It also clarifies that the first open pre-fills fields from the main profile, distinguishing it from update_my_guest_profile and other get_* profile tools.

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 opens with a clear when-to-use instruction ('改嘉宾资料之前先读现值') and provides an explicit call chain: list_my_invitations / respond_activity_invitation → this tool → update_my_guest_profile. This tells the agent exactly where the tool fits in a workflow and when to invoke it.

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