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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds genuine value beyond them: "Replace" signals wholesale overwrite of the existing recipient list, "Changes take effect immediately for published briefs" discloses timing, and the publish/invite exclusions prevent false expectations.

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?

Three tight sentences with the mutation and its scope front-loaded, followed by mode semantics and then the negative constraints. No filler, no repetition of the schema.

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?

With no output schema and no annotation coverage of timing or side effects, the description supplies exactly the missing pieces: replacement semantics, per-mode behavior, immediate effect on published briefs, and the explicit non-actions. An agent has everything needed to call it correctly.

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 description coverage is 0%, so the description must carry the burden, and it does for the important parts: it explains all three enum values of `mode` and clarifies that "specific" requires a listed verified email, which compensates for `emails` not being marked required in the schema. Only the `id` parameter is left unelaborated, which is self-evident.

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 ("Replace") and a precise resource ("access settings and the allowed recipient list") scoped to "one of your briefs." It is immediately distinguishable from the read-only sibling get_document_sharing and from publish_document, which it explicitly disclaims.

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?

Gives clear context: what each sharing mode means, that changes apply immediately to published briefs, and explicitly what the tool does NOT do (publish a draft, send invitations). It does not, however, name the counterpart tool for reading current settings, leaving that routing to inference.

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