tla_tex

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

No annotations are provided, so the description carries the full burden. It discloses the external dependency on LaTeX, but does not explain behavior on failure (e.g., missing LaTeX, invalid file) or whether files are modified. It adds some value beyond purpose but lacks depth.

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 concise at two sentences, no wasted words, and front-loads the core purpose. It is efficient and easy to parse.

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?

The description is largely complete given the high schema coverage and straightforward tool purpose. However, it lacks information about output behavior (e.g., file location, success indication) since no output schema is provided. Minor gap for a fully complete definition.

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?

The input schema has 100% description coverage, so the schema already documents all parameters. The description does not add any additional meaning or context beyond what is in the schema, maintaining the baseline score.

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 purpose: 'Typeset a TLA+ specification into a PDF or DVI file using TLATeX.' The verb 'Typeset' and the specific output formats distinguish it clearly from siblings like tlc_check or pcal_translate.

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 states when to use the tool (to typeset a spec) and a key prerequisite (LaTeX installation). However, it does not provide contraindications or explicit comparisons to sibling tools, though the sibling names offer implicit differentiation.

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