host_preview_restore

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

The annotations already declare readOnlyHint=true, and the description aligns by describing a 'preview' rather than an actual restore. It additionally adds context about original configuration and the protected copy being stored separately, which is useful behavioral information beyond the annotation.

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 sentences with the primary behavior front-loaded. It is compact and contains no filler, though the second sentence could be clearer about why the separate storage matters.

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?

With an output schema, readOnlyHint, and only two simple parameters, the description is reasonably complete. However, the unexplained 'scope' parameter and the lack of explicit guidance about the difference between previewing and applying a restore leave some contextual gaps.

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 0%, so the description must compensate. It indirectly relates the 'id' parameter to the backup identity from host_status, but it does not explain the 'scope' parameter or its default. This leaves the agent without adequate parameter-level guidance.

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 a specific action ('preview restore') on a specific resource ('the backup identity returned by host_status'), which clearly distinguishes it from host_apply. It is less explicit about how it differs from the sibling host_preview, but the mention of 'restore' provides enough differentiation.

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 the tool should be used after host_status returns a backup identity, so there is some contextual guidance. However, it does not explicitly state when not to use it, nor does it name alternatives like host_apply or host_preview.

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