Update an existing document (doc, word, note). Supply a new title and/or HTML content to replace the body.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| title | No | New title | |
| content | No | New HTML content (replaces entire document body) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses that content replaces the entire body, which is a key behavioral trait. However, it does not mention auth requirements, reversibility, error cases, or return format, so it is only minimally transparent.
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, front-loaded with the purpose, and no waste. Efficiently states what the tool does and what parameters are 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 simple mutation tool with no output schema and no annotations, the description covers the main purpose and behavior (replaces body). It lacks details on return values and error handling, but given the simplicity and high schema coverage, it is adequate.
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%, with each parameter described in the schema. The description adds the 'and/or' relationship between title and content, clarifying the combination, but does not add significant meaning beyond the schema.
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 clearly states the verb 'update', the resource 'document', and specifies the document types (doc, word, note) and what can be changed (title/content). This distinguishes it from sibling tools like create_document or append_to_document.
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 description implies usage for existing documents and mentions 'and/or' for title/content, but it does not explicitly contrast with alternatives like create_document or append_to_document. It lacks explicit when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct resource and action: document, sheet, tab, or presentation. Even similar operations like append_rows, append_slides, and append_to_document are clearly differentiated by their intended target.
The naming follows a predictable verb_noun pattern with create_, get_, list_, update_, delete_, and append_. Minor deviations like append_to_document (uses 'to') and the use of 'slide_presentation' vs 'slides' keep it from being perfectly uniform.
At 23 tools, the count is slightly above the ideal range, but each tool serves a clear purpose across three resource types (documents, sheets, slides). The volume is justified by supporting tab-level operations and append functionality.
The server provides full CRUD plus listing for each resource type, along with tab management and append operations. Minor gaps exist, such as lack of a direct 'set cell value' operation and no slide reorder or delete individual slide, but core workflows are well covered.