delete_all_page_layout_snapshots

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

With no annotations, the description should disclose behavioral traits. It only states the action (delete all) but does not mention irreversibility, side effects, permissions required, or status of snapshots after deletion. The description is insufficient for an agent to assess risks.

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, unambiguous sentence with no unnecessary words. It effectively communicates the core action and target.

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?

While the tool is simple, the description omits important context: what happens to the snapshots (permanent deletion?), any effect on other pages, and the meaning of 'all' in multi-page scenarios. An agent cannot fully assess the impact without more detail.

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 schema covers 100% of parameters with a description for 'pageIndex'. The tool description does not add any extra meaning or context (e.g., typical range, indexing convention). Baseline score of 3 is appropriate since schema provides basic coverage.

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 verb 'delete' and resource 'all layout snapshots for a page', clearly distinguishing it from 'delete_page_layout_snapshot' which targets a single snapshot. However, it could be more precise about what constitutes 'all layout snapshots'.

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 like 'delete_page_layout_snapshot' or other deletion tools. There are no when-to-use, prerequisites, or exclusion criteria mentioned.

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