sync

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

Discloses all behaviors: returns setup instructions if not configured, otherwise pulls remote work, commits local changes, and pushes. No contradiction with annotations (idempotentHint=true aligns with 'Safe to call repeatedly').

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?

Three sentences, front-loaded with main purpose, then usage and edge cases. No waste.

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?

Fully covers setup and normal operation; output schema handles return value details. Adequate for agent decision-making.

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 has 100% coverage for the single parameter remote_url, and description elaborates on its first-time-only usage and default behavior when omitted.

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?

Clear verb 'Sync' with specific resource 'memory vault with private git remote'. Uniquely distinguishable from sibling tools that perform different actions like checkpoint, consolidate, or search.

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: 'when the user wants their memory on another device, or to push/pull now.' Also provides setup instructions and notes that it's safe to call repeatedly.

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