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

Annotations already indicate readOnlyHint=false and destructiveHint=true, and the description adds meaningful behavioral context about the write-tier approval flow and the convention to call on the first clear ask without re-asking in chat. It does not contradict the annotations and surfaces the mutating nature of the operation.

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 core action is front-loaded in one sentence, followed by clearly separated routing and approval guidance. It is compact and useful, though the phrase 'the card is the yes' is somewhat cryptic and could be clearer.

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 simple three-parameter append tool with full schema coverage, this description is largely sufficient: it states the operation, common use cases, and approval behavior. It does not describe return values, but no output schema exists and the append operation likely does not require clarifying that.

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 100%, so the schema already documents doc_id, content, and companyId. The description does not add meaningful parameter-level detail beyond what the schema provides, so the baseline of 3 is appropriate.

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?

Description states the exact operation ('Append new content to an existing Google Doc') with a specific verb and resource. It is clear and naturally distinct from siblings like read_google_doc and create_google_doc, though it does not explicitly name them.

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 'Routing' line gives concrete use cases ('Add learnings to agent memory, append to a deliverable, or update a JD → use this'), which helps an agent decide when to invoke it. It also gives approval workflow guidance, but does not explicitly say when NOT to use this tool or which sibling to pick instead.

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