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

Beyond the thin annotation (destructiveHint=false), the description discloses meaningful behavior: a safe default preview of the real resource and opener, a hash-gated confirmation step, manual relay for cloud users, and the important caveat that establishing a conversation does not mean acceptance, group entry, or confirmed availability. This is substantial added context, though it doesn't cover failure modes or rate/permission constraints.

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 and semicolon-structured, front-loading the login precondition and the preview default before the commit instructions and caveats. Every clause carries information, though the compressed run-on style slightly reduces readability.

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 12-parameter mutation-with-confirmation tool with no output schema and minimal annotations, the description covers the workflow, most parameter meanings, the preconditions, and the practical caveat about conversation establishment. It is close to complete; only return-value expectations and edge-case behavior remain unstated.

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 0% schema coverage across 12 params, the description must carry the burden and largely does: it explains targetUserId's meaning for groups, and activityId, startsAt/endsAt (timezone-aware), headcount, and spaceName for venues, plus previewHash/consent/preview for the commit step. Only kind (enum semantics) and id are left to the schema, so the compensation is strong but not exhaustive.

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 establishes a specific resource and action through the mechanics: kind distinguishes group vs venue, targetUserId identifies the owner/admin/invitable person, and the preview→commit flow makes clear this is a contact/introduction request. The core verb 'contact the group owner or venue provider' is never stated as a sentence, so an agent infers the purpose from parameters rather than reading it directly.

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?

It gives a clear procedural usage path: default preview (preview=true), review the message, then resubmit the same params with previewHash, consent=true, preview=false. This tells the agent exactly how to use the two-phase flow. It does not compare against siblings such as community_resource_requests or request_ecosystem_venue, so the alternative-selection guidance is absent.

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