restore_workspace

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

With no annotations, the description carries full burden. It discloses the refusing-overwrites behavior, which is valuable, but it omits what 'verified' means, what happens if the workspace is not empty, and any other side effects. The transparency is partial, not complete.

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 two short, front-loaded sentences: the core action comes first, followed by the critical refusal behavior. Every word earns its place, with no redundancies 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?

Given no annotations, no output schema, and 0% parameter description coverage, the description is too sparse for an agent to call the tool correctly. It lacks parameter semantics, return behavior, and edge-case handling (e.g., what happens if the workspace isn't empty or the checkpoint isn't verified).

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?

The description gives no explanation of the 'project' and 'snapshot' parameters, and the schema provides 0% coverage (no property descriptions). An agent cannot infer valid values or how these parameters affect restoration, so the description completely fails to compensate for the missing schema documentation.

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 'restore' and the resource 'verified Drive checkpoint' along with the target 'empty workspace'. It also mentions a distinct behavioral constraint ('Refuses overwrites') that helps differentiate it from siblings like save_workspaces or prepare_workspace.

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 (restore a checkpoint into an empty workspace) and includes a precondition, but it does not explicitly compare with alternatives like list_checkpoints or save_workspaces. There is no when-not-to-use guidance or condition for choosing this tool over siblings.

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