sync_project

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

Annotations already declare this is non-read-only, idempotent, and non-destructive. The description adds value by revealing the underlying git pull behavior, which implies fetching and merging remote changes into the local working copy. This is more informative than a bare 'sync' label and does not contradict the 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?

One tight sentence conveys the core operation and the underlying mechanism. The parenthetical '(git pull)' immediately disambiguates the tool's meaning. There is no wasted or redundant wording.

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 sync tool with annotations already covering idempotency and destructiveness, the description is nearly complete. It could mention potential merge conflicts or return behavior, but the git pull framing gives an agent enough context to invoke the tool appropriately.

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%, and the project_id parameter is thoroughly documented in the schema, including format, source, and what it is NOT. The description itself contributes no parameter information, so the baseline of 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 names a specific verb ('Pull'), a specific resource ('Typleaf'), and clarifies the exact operation with '(git pull)'. This clearly distinguishes sync_project from siblings like download_source, upload_file, or write_files, which involve different remote/local data flows.

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 project_id parameter description explicitly states these tools are only for Typleaf projects, never for general local file I/O, and advises preferring standard read/grep tools when a local checkout exists. It does not name a particular sibling alternative for pulling changes, but the git pull framing makes the intended use obvious.

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