Compiles an Overleaf project and saves the resulting PDF locally, returning the status, local file path, and any LaTeX errors.
Compile the project on Overleaf and save output.pdf locally.
Returns status, local pdf_path on success, and parsed LaTeX errors.
| Name | Required | Description | Default |
|---|---|---|---|
| project | Yes | Project id (24-char hex) or exact name |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond those by stating that compilation saves a local artifact and returns status, pdf_path, and parsed LaTeX errors. No contradictions with annotations.
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 only two sentences with the primary action front-loaded and no filler. It states what happens, where the artifact lands, and what is returned, all efficiently.
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 full schema coverage, relevant annotations, and an output schema, the description is complete. It covers the action, target, local side effect, and return values without needing to re-explain structured schema details.
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 single 'project' parameter is already documented as 'Project id (24-char hex) or exact name'. The description adds no additional parameter-specific semantics, so the baseline score of 3 applies.
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 specific action ('Compile'), the target resource ('the project on Overleaf'), and the concrete outcome ('save output.pdf locally'). This distinguishes it well from sibling tools like download_pdf, which presumably retrieves a PDF rather than compiling a project.
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 makes it clear the tool is for compiling a project and getting a local PDF, which is sufficient context for an agent. However, it does not explicitly contrast with download_pdf or mention when to avoid using this tool, so it stops short of full alternative-routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.