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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds real context: it is a full replacement of prior access settings and the recipient allowlist, changes apply immediately for published documents, it neither publishes drafts nor sends invitations, and it deliberately returns no individual reader emails. That is the kind of side-effect and return-scope disclosure annotations cannot express.

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 trigger and mode semantics are front-loaded and earn their place, but the middle-to-late portion drifts into dashboard features (pre-view name/email/phone capture, passcodes, expiration) and repeats mode caveats already present in the schema. Several of these sentences are tangential to invoking this specific tool, so the definition is longer than needed.

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 3-parameter mutation tool with no output schema, the description covers side effects, immediate effect timing, scope of replacement, and what is not returned, which is more than adequate. It stops short of only trivial detail, and the mode/email specifics live in a fully-covered schema.

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 baseline is 3, but the description still earns credit: it explains that public mode allows anyone with the link while verified/specific require a verified sign-in, and that 'emails' is an allowlist that fully replaces the previous list rather than a lead report. The 50-item cap and per-mode requirement are left to the schema, so it is not a full 5.

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 opens with a concrete trigger plus the three access outcomes it sets (link-anyone, sign-in-required, listed-emails), which is a specific verb+resource statement. It is clearly separable from get_document_sharing, update_document_reader_settings, get_document_leads and publish_document because it names what it does not do (no publishing, no invitations, no email reporting).

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 states when to use it ('when the owner wants to make a document accessible...') and when not to ('Does not publish a draft or send invitations'), and it routes the agent elsewhere for adjacent concerns by naming the dedicated reader-settings and explicit-request activity/lead tools. The only minor softness is that the alternatives are named by category rather than by exact tool name.

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