overleaf_pull

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It explicitly discloses a critical side effect: overwriting existing files in dest_dir. This is valuable and better than a generic 'download' statement, though it omits other details like permissions or error behavior.

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 entire description is one sentence that leads with the action, specifies the destination, and includes an important caveat. Every word earns its place, with zero redundancy or filler.

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 focused tool with only two well-documented parameters and an output schema, the description covers the core operation and a key destructive consequence. It is concise but leaves out explicit alternative guidance, which is minor given the simplicity of the operation.

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 already provides 100% coverage for both parameters, including clear descriptions for 'project' and 'dest_dir'. The description adds no additional parameter-level meaning beyond what the schema states, which aligns with the baseline score of 3 for full schema coverage.

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 uses a specific verb ('Download') and resource ('Overleaf project') plus a destination ('dest_dir'), clearly distinguishing this from siblings like overleaf_download_pdf (PDF only) and overleaf_push_file/push_dir (uploads). It accurately conveys the pull/extract operation.

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 implies usage when a full project download is needed, and the overwrite warning hints at caution, but it does not explicitly state when to prefer this over siblings or mention exclusions. Clear context exists, but no direct alternatives or when-not guidance is provided.

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