Render LaTeX preview

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

With no annotations provided, the description fully carries the burden. It reveals key behaviors: uses local TeX or WASM, updates live preview, returns compile success/errors, engine, backend, file count, and preview URL. There is no mention of destructive actions, but that aligns with a preview tool.

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 efficiently structured: first sentence states purpose, second explains backend, third lists returns, fourth gives usage advice. It contains no fluff, though some sentences are slightly long. Every sentence contributes value.

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 no output schema, the description adequately explains return values (success/errors, engine, backend, file count, preview URL). It also covers the live update behavior. It does not detail error formatting or edge cases, but covers the essentials.

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 the schema already documents all parameters well. The description adds no significant parameter-specific detail beyond the schema; it only provides general context. 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 clearly states the tool's action: 'Compile the current project's LaTeX to a PDF locally and update the live preview.' It identifies the specific resource (LaTeX project) and verb (compile/preview), and is well differentiated from sibling tools which are about comments and diffs.

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 explicitly says 'Call this after editing .tex files to see and verify the rendered result,' giving clear usage context. It does not specify when not to use it or provide alternative tools, but siblings are distinct enough to avoid confusion.

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