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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description earns credit by disclosing the non-obvious side effect: the tool writes the theme as the shop's draft. That explains the destructive flag for a tool whose name suggests a pure read. It still omits reversibility, whether the draft can go live, and auth requirements.

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?

A single front-loaded sentence that states the mutation first and the return value second. No padding, and the 'so you can see what you built' clause is a compact purpose statement rather than filler.

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?

No output schema exists, so the description usefully states the return (a screenshot of one page). Combined with the staging disclosure, an agent knows both the side effect and the output. It could go further on the screenshot's format/lifetime and the permanence of the staging, but it is largely sufficient.

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 100%, with page, slug and width all documented (including the template handle list and width semantics). The description adds nothing beyond the schema, so the baseline 3 applies.

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 gives a specific compound verb+resource: it stages a theme as the shop's draft and returns a screenshot of one page. This is clear and even corrects a misleading name (a 'screenshot' tool that actually mutates state). It does not, however, distinguish itself from the sibling stage_own_theme, which appears to overlap in the staging behavior.

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?

Usage is only implied by the trailing clause 'so you can see what you built' — i.e., use it to preview a theme you authored. There is no explicit when-to-use/when-not, and the obvious alternative (stage_own_theme, check_own_theme) is never named, leaving the agent to infer which staging/preview tool to pick.

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