Compile the LaTeX project in a specified directory into a PDF using Tectonic, returning the output PDF path and compiler logs.
Compile main.tex in project_dir with Tectonic.
pdf_path is None if compilation failed to produce a PDF. log_text always
contains the full compiler output so the caller can diagnose and fix the
source before retrying.
| Name | Required | Description | Default |
|---|---|---|---|
| project_dir | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that pdf_path is None on failure and that log_text always contains full compiler output, giving the agent diagnostic guidance. It does not discuss side effects, but for a compile operation this is adequate.
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 with no filler. The first sentence states the core action and the second adds essential failure/diagnostic behavior. Information is front-loaded and 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 simple one-parameter compile tool with no output schema, the description covers the critical return behaviors: failure signaling via pdf_path and diagnostic availability via log_text. It could be slightly more explicit about the success value of pdf_path, but it is otherwise complete.
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 0%, so the description must compensate. It does by clarifying that project_dir is the directory containing main.tex to compile. This adds meaningful semantics beyond the bare 'Project Dir' schema label.
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 ('Compile main.tex'), the target location ('in project_dir'), and the tool used ('with Tectonic'). This clearly distinguishes it from sibling file/read/write/render tools.
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 purpose makes the intended use obvious, but the description does not explicitly state when to prefer this tool over alternatives or mention any exclusions. Usage context is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.