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

Beyond the annotations, the description discloses rich behavioral traits: login requirement, exact channel behavior (APP sends in-app invite, SMS sends real SMS, MANUAL prepares a dedicated link and grants activity visibility), that phone numbers are not returned, the preview-then-execute flow requiring previewHash and preview=false, and that failures should not switch channels. These details substantially exceed the annotation coverage without contradicting readOnlyHint=false, destructiveHint=false, or openWorldHint=true.

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 dense but well-structured into two bracketed sections: first the login and channel behavior, then the required preview execution chain. Every sentence carries information, though the packed formatting and lack of spacing make it slightly less front-loaded than ideal.

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?

Given the mutation, login requirement, preview workflow, six parameters with nested recipients, and no output schema, the description covers most critical aspects: authentication, channel side effects, preview confirmation steps, failure behavior, and output privacy (phone number not returned). Minor gaps remain around required recipient limits and resend semantics, but the description is largely complete for correct invocation.

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?

With 67% schema description coverage, the description adds useful meaning for the channel enum by explaining what APP, SMS, and MANUAL actually do, and it clarifies execution semantics for preview and previewHash. It does not compensate for undocumented parameters such as activityId and the nested recipients fields (userId, resend, max 6 items), so the added parameter guidance is partial.

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 clearly states a specific verb and resource — inviting a matched pair to an activity — and even details the invitation channels (APP, SMS, MANUAL). However, it does not explicitly distinguish this tool from sibling tools like invite_organization_meetup_to_activity or list_organization_match_invite_activities, leaving the agent to infer routing from the name alone.

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 outlines a required workflow (details channels + invitable activities → preview → user confirmation → execute with previewHash and preview=false) and notes login is required, which gives implied usage context. It does not, however, state when to choose this tool over alternatives or provide explicit exclusions, so the guidance remains incomplete.

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