get_ui_snapshot

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

With no annotations provided, the description carries the full burden. It adds useful context (internal, for UI recovery, LLM not needed) and implies a read-only snapshot, but does not explicitly state side effects, authentication, or rate limits. Adequate for a simple retrieval tool, but not rich.

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?

Two sentences, front-loaded with the core purpose and immediately followed by the critical non-usage note. No wasted words; every sentence earns its place.

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?

For a single-parameter tool with no output schema and clear purpose, the description is nearly complete. It explains why it exists, when to use it, and when not to. Minor gap: doesn't describe the snapshot structure, but it's a simple retrieval of preview responses, so this is not critical.

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 coverage is 100%, and the parameter 'resource_uri' is already fully described with an enum and clear semantics. The tool description adds no extra meaning about the parameter, so baseline 3 is appropriate.

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 a specific action ('returns the snapshot of recent preview tool responses') for a specific resource (confirmation UI iframe), and clearly distinguishes it from the many analysis siblings by marking it as internal and for UI recovery. The purpose is unambiguous.

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?

Explicitly states when to use (UI self-recovery when host doesn't deliver tool-result notifications) and when not to use (LLM response generation), and points to the alternative (preview tool responses contain the same content). This is direct, actionable guidance.

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