sync_desktop

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

No annotations are provided, so the description must fully disclose behavioral traits. It explains the incremental behavior and the first-call full import. It also mentions a dependency (sqlcipher). However, it does not detail side effects (e.g., whether it modifies local store), authentication needs, or error conditions. This is adequate but not exhaustive.

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 three sentences, each serving a distinct purpose: what it does, performance on repeat, difference on first call, and a prerequisite. It is front-loaded with the core action and efficiently adds key context without extraneous details.

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?

Given the tool has no parameters and no output schema, the description covers the essential behavioral aspects: incremental sync, first-call behavior, and a requirement. It could be slightly more complete by mentioning expected behavior if no prior sync exists or what happens if sqlcipher is not available, but overall it is sufficiently complete for a simple tool.

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 has zero parameters, so the description need not add parameter details. The baseline with high schema coverage is 3, but the description's lack of parameter information is appropriate given no parameters exist. It implicitly adds value by explaining the tool's behavior without needing to describe parameters.

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 it performs incremental sync from Signal Desktop, importing only newer messages. This distinguishes it from sibling tools like import_desktop, which presumably does a full import. The verb 'sync' and specification of incremental nature provide high purpose clarity.

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: for incremental updates after an initial sync. It contrasts first call behavior (full import) with repeat calls (fast, only new). It also notes the prerequisite 'Requires sqlcipher'. While it doesn't explicitly say 'use this instead of import_desktop for incremental updates', the context of siblings makes this clear.

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