sync_trigger

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

With no annotations, the description carries full burden. It reveals asynchronous behavior ('starts immediately but completes asynchronously'), side effects ('triggers a sync request'), and return value ('Returns meta.syncPending = false'). Lacks details on error handling or concurrency if sync already pending, but overall transparent.

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?

Four concise sentences, front-loaded with purpose, followed by usage guidelines and behavioral details. No redundant words. Every sentence adds value. Example call included.

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 zero-parameter tool with no output schema, the description covers all necessary context: purpose, when to use/avoid, behavior (async, side effects), return value, and example. Differentiates from sync_status sibling.

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?

No parameters exist, so baseline is 4. The description adds no parametric detail, but none is needed. It focuses on behavior and usage, which is appropriate given zero 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?

Description clearly states the action ('Kick off an OmniFocus sync') and resource ('Omni Sync Server'). It distinguishes from sibling tool sync_status by focusing on initiating sync, not checking status. The verb 'kick off' is specific and actionable.

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?

Explicitly states when to use ('after any sequence of mutations when you need changes on other devices') and when not to use ('Do not call when no mutations have been made; prefer checking meta.syncPending first'). Provides clear alternatives and context.

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