overleaf_download_pdf

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds an important ordering dependency (compile must succeed first) and reveals where the file is saved: OVERLEAF_DATA_DIR/workspace/pdfs/<project_id>/. It does not cover overwrite behavior or error cases, but the essential behavioral traits are transparent.

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 one dense, well-structured sentence. It front-loads the core action, then supplies the prerequisite and save location without any filler or repetition.

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 two-parameter download tool with no annotations and no output schema, the description is mostly complete: it states the action, prerequisite, and destination. It could mention what happens on failure or what the tool returns, but those are minor gaps given the tool's simplicity.

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 baseline is 3. The description adds a little context about the save destination and the human-readable filename aspect, but it does not substantially enrich the parameter meanings beyond what the schema already provides.

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 a specific action ('Download the latest compiled PDF') and resource, distinguishing it from the generic sibling overleaf_download_file. The phrase 'latest compiled PDF' precisely identifies what this tool produces.

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 instructs to call overleaf_compile first and to download only after a successful compilation, which is strong when-to-use guidance. However, it does not explicitly mention when not to use it or name alternatives like overleaf_download_file for downloading individual project files.

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