restore_page_style_from_snapshot

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

With no annotations, the description carries the full burden but only states 'Restore', implying mutation without disclosing side effects, permissions, or behavior like polling (wait_ms, poll_ms). It does not explain whether the restore is incremental or replaces all state.

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 sentence with no redundant words. It efficiently conveys the core purpose and the optional filtering aspect.

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 four parameters (0% schema coverage), no annotations, and many siblings, the description is insufficient. It omits details about the snapshot format, coordinate filtering, polling behavior, output, and use cases.

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 only partially explains the coords_json parameter as 'filtered to selected coordinates'. It does not clarify the meaning of name (snapshot file name), wait_ms, or poll_ms. With 0% schema coverage, the description fails to compensate.

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 specifies the action 'Restore' and the resource 'button style state from a saved snapshot file', and mentions optional filtering by coordinates. It distinguishes from sibling tools like restore_page_style_from_inventory by indicating a file-based source.

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?

No guidance is provided on when to use this tool versus alternatives such as restore_page_style_from_inventory or load_page_style_preset. There is no mention of prerequisites, context, or when not to use it.

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