acc_restore_folder

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

The readOnlyHint=false annotation already signals a mutating operation, and the description adds the context that the folder is hidden. It does not disclose side effects (e.g., restoring contents, permissions) or any requirements, but it also does not contradict the annotations.

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 a single, front-loaded sentence that conveys the essential action without unnecessary words. Every word earns its place.

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 restore operation with two well-described parameters and an output schema, the description is mostly sufficient. It could be slightly richer by noting that the folder becomes visible again or that it restores to its original location, but the current text adequately conveys the core function.

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%, with both folder_id and project_id clearly described as 'Folder URN' and 'Project id'. The description adds no additional meaning beyond the schema, which already fully documents the parameters.

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 uses the specific verb 'Restore' with the resource 'folder', and specifies 'previously deleted (hidden)' to clarify the exact target. This clearly distinguishes it from sibling tools like delete, create, or rename.

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 phrase 'previously deleted (hidden) folder' implies the primary use case: undoing a deletion. However, it does not explicitly state when to use it vs. alternatives, nor does it mention any prerequisites or exclusions (e.g., folder must be in hidden state).

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