restore_selected_page_style_from_inventory

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

No annotations are provided, so the description carries full burden. It fails to disclose behavioral traits such as whether the operation is destructive, permissions needed, rate limits, or side effects. The description is too minimal for a mutation tool.

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 very short but at the expense of necessary details. It is under-specified rather than concise, failing to earn its place by omitting crucial information.

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 tool has 4 parameters, 2 required, no annotations, and an output schema, the description is inadequate. It does not explain parameters, the meaning of coordinates, or the purpose of wait_ms/poll_ms, nor does it hint at the output.

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%, and the description does not explain any parameters (inventory_json, coords_json, wait_ms, poll_ms). It adds no value beyond the schema, leaving the agent to guess what coordinates mean or how to format them.

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 tool restores only selected coordinates from a captured page inventory, using a specific verb and resource. It distinguishes from sibling tools like restore_page_style_from_inventory by indicating partial restoration.

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 for partial restoration via 'only selected coordinates', but lacks explicit guidance on when to use versus alternatives, no when-not scenarios, and no mentions of alternatives or prerequisites.

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