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

Annotations only flag destructive/read-only/idempotent hints; the description adds critical behavioral facts: the action is irreversible once delivered ('真送达主办方且不可撤回'), requires confirmation before sending, contactMode SHARE transfers contact info to the organizer, and accepting an audience invite auto-registers the user. This is far beyond annotation coverage.

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 compactly organized with labels (需要登录/何时用/组合链/口径) and numbered rules. Every segment adds operational value, and the highest-priority safety/privacy constraints are front-loaded.

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?

Despite no output schema, the description explains the post-accept flow (profileNeeded → update_my_guest_profile), the irreversible delivery, the privacy default for contactMode, and the auto-enrollment side effect. For a destructive, privacy-sensitive invitation response tool, this is complete enough for an agent to act 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 description coverage is 0%, so the description carries the burden. It explains accept/decline semantics, reason as the '婉拒理由', and contactMode SHARE vs IN_APP with privacy implications; invitationId is contextualized via list_my_invitations. It does not mention the optional note parameter, but the most decision-critical parameters are covered.

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 states a specific, user-triggered action ('用户明确说「这场接/这场推掉」时替他回应') on the activity-invitation resource, so it is not a tautology. It does not explicitly name sibling tools to exclude (e.g., respond_collaboration_invite), relying on the title/context for resource distinction.

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?

Gives an explicit trigger condition ('when user explicitly says accept/decline') and a combination chain with list_my_invitations and update_my_guest_profile. It lacks explicit when-not-to-use or named alternatives, but the context is clear enough.

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