sync_now

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 details that the tool performs a two-way reconcile, propagates already indexed content, and returns JSON with status, peers, and file_sync. It also explains conditions that cause nothing to run (disabled or no target), which fully discloses 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 description is concise and well-structured: a lead sentence stating the main action, followed by details on execution, usage guidance, possible returns, and failure conditions. Every sentence adds value without redundancy.

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 zero parameters and the presence of an output schema (mentioned in description), the description covers all necessary aspects: what it does, when to use, prerequisites, return structure, and edge cases. It is fully complete for an agent to invoke correctly.

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 tool has zero parameters (empty schema), so the baseline is 4. The description does not need to add parameter details; the schema coverage is 100% by virtue of no 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 the tool syncs Memex with other devices via two-way reconcile with paired peers and shared folder. It distinguishes itself from sibling tools like index_terminal_sessions, which is a prerequisite. The verb 'sync' and resource 'Memex with devices' are specific and unambiguous.

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 says when to use (user asks to sync/push/send) and provides prerequisites (sync must be enabled, call index_terminal_sessions for current session). It also explains when nothing runs, offering clear guidance on when not to use this tool.

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