Sync All

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

Despite no annotations, the description discloses the delta-cursor mechanism, what data is refreshed each run, and what happens on re-run ('Upserts by expense id, so re-running is safe'). It also mentions 'Returns counts,' covering a practical side effect beyond the input schema.

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 concise, information-dense sentences front-load the purpose, then detail sync behavior and safety. No filler; every sentence contributes.

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?

With one simple boolean parameter, no annotations, and an output schema present, the description covers the sync semantics, idempotence, and first-run behavior. Nothing an agent needs to decide or call correctly is missing.

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, full, is undocumented in the schema (0% coverage), but the description explains it directly: 'first run, or full=True, pulls everything' and implies the default delta behavior. This fully compensates for the empty schema descriptions.

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 opens with 'Sync Splitwise into a local SQLite mirror for instant offline search,' naming the verb, resource, and purpose. The delta-sync mechanism makes it distinct from sibling query tools like get_expenses or search_expenses, so an agent can differentiate it without opening the schema.

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?

It clearly frames the tool as the offline-mirror/sync option ('for instant offline search') and explains when a full pull happens ('first run, or full=True'), plus idempotence ('re-running is safe'). It does not explicitly name alternatives or give when-not-to-use guidance, but the context is clear enough.

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