Update a doc’s name and/or folder

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

With no annotations, the description carries full burden for behavioral disclosure. It reveals that expectTitle is verified against the live doc and nothing is changed on mismatch, which is useful. However, it does not mention permissions, reversibility, or response format, leaving some transparency gaps.

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 description is concise, using three sentences that are front-loaded with the primary action. Each sentence provides necessary context without redundancy or filler.

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?

The description covers the core functionality, parameter interactions, and the important distinction from content-editing tools. It lacks some details like return values or permission requirements, but given the absence of an output schema and the relatively simple scope, it is adequately complete for an agent to use effectively.

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 80%, so baseline is 3. The description adds value by explaining that folder can be a URL or id, and that expectTitle serves as a verification safeguard. It also clarifies the relationship between name and folder (provide at least one).

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?

Clearly states it updates a Google Doc's metadata (rename and/or move), using a specific verb and resource. It distinguishes itself from content-editing tools by explicitly naming edit_doc/overwrite_doc as the alternatives for content edits.

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?

Provides explicit guidance on when to use this tool versus edit_doc/overwrite_doc for content edits. It also explains the input requirements (provide name, folder, or both) and the special condition when moving (expectTitle must be passed).

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