ck_sync_transactions

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

Annotations only indicate readOnlyHint:false, so the description carries the burden of explaining mutation. It goes beyond by detailing the incremental fetch range (last sync + 30-day overlap), automatic token/MFA handling, and the bounded/resumable contract with another_run_needed:true. This is rich behavioral disclosure that annotations alone cannot provide.

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, each earning its place: purpose and scoping, authentication behavior, and pause/resume semantics. Information is front-loaded with the core purpose, followed by essential behavioral details. No fluff or repetition.

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 no output schema, the description explains key side effects and return indicators (another_run_needed:true). However, it does not detail the full return shape or what happens to pre-existing local rows (e.g., upsert vs. append), which is relevant for a sync tool. Still, the main operational aspects are covered, making it mostly complete.

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?

Input schema already has 100% coverage with descriptions for both max_pages and force_full. The description adds valuable context, such as max_pages overriding the CK_SYNC_MAX_PAGES environment variable and the meaning of omitting it (unbounded sync). This extra semantic layer beyond the schema earns a score above baseline.

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 Credit Karma transactions into the local SQLite database' – a specific verb (sync) and resource (transactions into local DB), clearly distinguishing this from siblings that merely list/get data. It also specifies the incremental default behavior, further clarifying its role.

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?

Provides clear context on when it runs (incremental with overlap) and automatically handles auth via login/MFA. It also explains the bounded/resumable behavior with another_run_needed, but does not explicitly contrast with sibling tools or state when to prefer this over ck_list_transactions, so it falls short of full usage guidance.

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