Rename file or folder

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

Beyond the destructiveHint annotation, the description discloses queued behavior (returns RequestId, completes in background under 2 minutes), the need for confirm=true, and the RBAC/authorization nuance (denial means scope issue, not tool failure). This adds significant behavioral context that the annotations alone do not provide.

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 four sentences and front-loads the core purpose. Each sentence adds meaningful information (addressing, queueing, destructiveness, auth). It is slightly dense and repeats the storageId caution that already exists in the schema, but overall it is efficient and well-structured.

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 mutating tool with no output schema, the description covers key aspects: how to address the object, queued async behavior, verification strategy, confirmation requirement, and auth context. It does not describe the preview return when confirm=false or error scenarios, but these are partially inferable from the schema and annotations. The description is sufficiently complete for an agent to invoke the tool 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 coverage is 100%, so the baseline is 3. The description reinforces the storageId distinction (from indexed tools, not list_files) and mentions required fields, but most parameter-level meaning is already present in the schema descriptions. The addition of queued behavior and confirm semantics is more behavioral than parameter-specific, so no strong uplift beyond baseline.

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 states 'Rename a file or folder in a drive' with a specific verb and resource, and immediately clarifies the addressing scheme (exact object key plus storage id). It distinguishes from sibling tools like move_file and duplicate_file by focusing on key renaming, and explicitly notes the storage id source differs from list_files, eliminating ambiguity.

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 provides clear when-to-use context: it explains the storage id must come from indexed listing tools, not list_files, and says to verify by listing until the new name appears. It also states prerequisites (drive/bucketName) and the confirm requirement. However, it does not explicitly contrast with alternatives like move_file or duplicate_file, leaving some inference to the agent.

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