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

Annotations supply only readOnlyHint=false, so the description carries most of the burden — and it does disclose the non-obvious two-phase behavior: calling without confirm:true returns a preview rather than creating anything. That is genuinely useful safety context. It stops short of saying whether links can be revoked, who may create them, or what the response contains.

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?

A single tight sentence plus a parenthetical that front-loads the most important operational fact (preview-until-confirm). Every clause earns its place, though 'with an optional name/phone' partly repeats what the schema already shows.

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 mutation tool with no output schema, a nested input object whose fields lack descriptions, and a preview/execute dual mode, the description covers the core action and the confirm gate but says nothing about the returned link, its lifetime, or how it relates to the other invite/link tools. Enough to call it, not enough to call it confidently in edge cases.

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 50%: `confirm` is documented in the schema itself, and the description restates its semantics, while the nested `name`/`phone` are mentioned but `expiresInHours` — the parameter with a meaningful 1–2160 range — is never explained in the description. Adequate, but it leaves the most consequential input undocumented.

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 and resource — 'Create a shareable client invite link' — plus the channel ('for WhatsApp') and optional inputs, which is far more informative than a bare 'create_invite_link'. It does not, however, distinguish itself from close siblings such as create_client_portal_link, create_plan_share_link, or invite_client_to_organization, which an agent could easily confuse it with.

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 'for WhatsApp' qualifier and the confirm-gating note imply the context of use (send a client a WhatsApp-joinable link), but there is no explicit when-to-use/when-not statement and no named alternative for the other link/invite tools in the sibling set.

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