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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is known. The description adds genuine value beyond that by naming the concrete consequence — the email is sent immediately and cannot be recalled — which tells the agent the effect is externally visible and irreversible. It stops short of mentioning required permissions or rate limits.

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?

Two sentences, zero waste, and the operative content (what is sent to whom) is front-loaded ahead of the caution about irreversibility. Nothing is padded or repeated.

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?

An output schema exists, so return values need not be explained, and the description covers the action plus its irreversible external effect. The only material gaps are unstated prerequisites (whether the page must be published first) and no cross-reference to notify_recipients, which is a plausible competing choice.

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 100%, so the schema already documents all four parameters including defaults (7 days, 0 = never expire) and the personal-link-per-recipient behavior. The description only restates 'optional message and access expiry,' adding no syntax or format detail beyond the schema. Baseline 3 applies when structured fields carry the semantics.

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 (email) and resource (personal invitations for a page) with the scoping detail 'to the specified recipient addresses.' It is clearly distinct from read tools like get_page and list_pages, though it does not explicitly differentiate itself from the nearby sibling notify_recipients, which an agent might reasonably 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?

Usage is only implied: an agent can infer this is for sharing a page by email, but there is no explicit when-to-use statement, no condition distinguishing it from notify_recipients, and no stated prerequisites (e.g., must the page be published first?). The line about immediacy and irreversibility is a caution rather than routing guidance.

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