Sync Overleaf project

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 that Overleaf git access is a premium feature, that failure is cached, and that a normal 'unavailable' result is returned instead of an error. However, it does not warn about potential side effects like overwriting local files during pull.

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 two sentences, but the first word 'Optional.' is somewhat ambiguous and could be removed or clarified. Overall, it is fairly concise and front-loaded with the main action.

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 covers the main purpose and behavior regarding availability and caching, but it lacks details on the return value format (e.g., what 'list the .tex files' means in terms of output). Given no output schema, more context would be beneficial.

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%, so both parameters are already described in the schema. The description adds no new information beyond what the schema provides (e.g., 'force' and 'project' descriptions are identical). Baseline 3 is appropriate.

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 action: 'Clone (or pull) your Overleaf project via its git repo and list the .tex files.' It uses a specific verb (sync) and resource (Overleaf project), and distinguishes it from the sibling tool overleaf_commit_push.

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 explains when to use the tool and provides guidance: if the feature is unavailable, it returns an 'unavailable' result (not an error) and the agent should continue with local templates. However, it does not explicitly compare to alternatives like overleaf_commit_push.

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