sync_tasks

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

With no annotations provided, the description fully covers behavior: pushes/pulls changes, conflict resolution (server-side, local changes not lost but reordered), and role requirement (MANAGER). It also indicates error conditions and dry_run effects.

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 extremely concise—three sentences covering purpose, prerequisites, behavior, and parameter. No unnecessary words, and the most important information appears first.

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's simplicity (one parameter, output schema exists), the description covers everything: purpose, prerequisites, behavior, parameter usage, and role requirement. No gaps remain.

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 only parameter, dry_run, has 0% schema coverage, but the description fully explains its meaning: 'Supports dry_run=true to check connectivity without transferring data.' This adds essential semantic context beyond the schema.

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 purpose: 'Trigger a sync with the configured TaskChampion sync server.' It uses a specific verb and resource, and distinguishes itself from siblings which are all CRUD or analysis tools, none of which perform sync.

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 provides explicit prerequisites: 'Requires a TaskChampion sync server configured in .taskrc. Returns an error if no sync server is configured.' It also mentions the dry_run option for checking connectivity, giving clear guidance on when 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.