preview_restore_page_style_from_snapshot

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

With no annotations, the description must disclose behavioral traits. It only states it's a 'preview', implying non-destructiveness, but does not mention authentication needs, side effects, or what the output contains. The existence of an output schema is not leveraged in the description.

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, concise sentence with no waste. However, it is very brief and could benefit from additional details without sacrificing conciseness.

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 the presence of many sibling preview tools, the description is incomplete. It does not explain what a 'restore plan' is, what the preview returns, or how coordinates work. The output schema exists but is not referenced, leaving the agent with insufficient context.

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 hints that 'coords_json' relates to coordinates for filtering, but does not explain its format or the purpose of 'name'. The meaning added is minimal beyond the schema itself.

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 'Preview' and the resource 'restore plan from a saved snapshot', distinguishing it from similar sibling tools like 'preview_restore_page_style_from_inventory' which uses inventory instead of snapshot. The optional filtering by coordinates is also mentioned, adding specificity.

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 when to use this tool (when a saved snapshot exists) but does not explicitly compare with alternatives like 'preview_restore_page_style_from_inventory'. No when-not-to-use guidance is given, leaving selection among many preview siblings to the agent's inference.

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