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

Annotations only declare readOnlyHint/openWorldHint/destructiveHint; the description goes well beyond that by disclosing that external requests and browser storage are unavailable, that output is an unsaved draft requiring the user's Save locally button, that id reuse is expected on revision, and by warning the agent never to claim the app was saved. The 'unsaved draft' framing is consistent with the read-only annotation rather than contradicting it.

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?

Five short sentences, each carrying distinct information, with the core purpose front-loaded and the constraints following in priority order. The final 'never claim saved or published' line slightly restates the draft point but functions as an important behavioral guardrail, so it still 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?

With no output schema and thin annotations, the description adequately covers sandbox limits, draft semantics, id reuse, and expected inlining. It does not say what a failed render returns or how the preview modes change behavior, which are the remaining gaps for a five-parameter 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 0% for five parameters, so the description carries the full burden and only partly delivers: it implies the id (reuse on revision) and constrains code to inline CSS/JS, but name, previewMode and duoPosture are never explained, nor is the enum meaning of the latter two.

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 opens with a concrete verb+resource: 'Render a complete self-contained HTML app in iPadian', which tells an agent exactly what the tool produces. It is clear and specific, but it never mentions the sibling open_ipadian, so differentiation must be inferred from the tool names alone.

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 context is strong: it states the sandbox limitations (no external requests, libraries, storage, navigation), instructs to keep the same id when revising an app, and clarifies the draft lifecycle. It stops short of explicit when-not-to-use routing against open_ipadian, so it sits just below the top score.

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