Remount Viewer

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

Annotations are minimal (destructiveHint=false, etc.). The description adds that 'Any user highlight is cleared on remount', which is a side effect beyond what annotations provide. This helps the agent understand the tool's impact.

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?

Three sentences: purpose, context, side effect. No unnecessary words. Information is front-loaded and earned.

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 2 params and an output schema, the description covers purpose, invocation context, and a side effect. It could mention error cases (e.g., invalid viewUUID) but is otherwise complete for a straightforward tool.

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%, so baseline is 3. The description adds little beyond schema: it mentions 'preserving viewUUID' which reinforces viewUUID's role, but does not add new semantic detail.

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 states 'switch the viewer to a different artwork while preserving the viewUUID', which is a specific verb+resource. It distinguishes itself by noting it is internal and called during in-viewer navigation, but does not explicitly differentiate from sibling 'navigate_viewer'.

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 says 'Called by the artwork-viewer iframe during in-viewer related navigation', implying usage context, but provides no exclusion criteria or alternatives. Sibling 'navigate_viewer' exists but no guidance on when to use which.

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