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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful precondition that the folder must be visible and writable. However, it says nothing about idempotency/retry behavior even though the tool takes an idempotencyKey and the idempotentHint annotation is false — an area where extra context would be valuable.

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?

A single, front-loaded sentence with no wasted words. It is efficient, though the brevity comes at the cost of the missing guidance scored elsewhere.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety and idempotency profile. For a mutation tool with three required parameters, though, the description omits retry semantics, the consequence of the rename, and any disambiguation from the sibling rename/restore folder tools.

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%; name and idempotencyKey are documented in the schema, but folderId carries no description. The description adds no parameter meaning at all — no note on the name constraints, folderId format, or contract of the idempotency key — so it fails to compensate for the uncovered parameter.

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?

"Rename a visible, writable sheet folder" gives a specific verb (rename) plus the resource (sheet folder), which separates it from the many sheets_rename* siblings that act on sheets, columns, or versions. The "visible, writable" qualifier narrows scope further. It stops short of naming any sibling explicitly, so an agent must still infer the sheet-vs-folder distinction.

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 states a precondition (the folder must be visible and writable) but gives no when-to-use guidance, no alternatives, and no reference to related tools like sheets_rename, sheets_move_to_folder, or sheets_create_folder. An agent gets no routing help beyond the tool name itself.

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