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

Annotations already flag destructiveHint=true and openWorldHint=true; the description goes beyond them by explaining what is destroyed ('A new link replaces the current file') and the failure mode ('it takes effect only if Conciergr can read it'). It also discloses the sharing/permission prerequisite, which is exactly the kind of context structured fields can't carry.

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?

Four short sentences, each carrying distinct information: purpose and slots first, then the prerequisite, then format restriction, then replacement/validation semantics. No filler or restatement of the name.

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 destructive, open-world mutation with no output schema, the description supplies the preconditions (sharing, real Google format), the effect on existing state (replacement), and the success condition (must be readable). Nothing an agent needs before calling is missing.

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 67% and the `slot` enum has no schema description; the description fills precisely that gap by mapping sheet to classes/schedules/fees and doc to policies/FAQs. `url` and `brand` are already documented in the schema, so the description adds nothing further there.

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 ('Link or replace the assistant's Google Sheet ... or Google Doc') and defines what each slot holds (sheet: classes, schedules, fees; doc: policies, FAQs). It doesn't explicitly differentiate itself from sibling tools like save_document or remove_document, so the agent must infer that boundary, but the core operation is unmistakable.

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 concrete prerequisites — share the file with `shareEmail` from get_overview as Viewer first, and it must be a genuine Google Sheet/Doc rather than an uploaded Excel or Word file. That is clear guidance on when the call will succeed, though it never names an alternative tool or an explicit when-not condition.

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