Sync transactions (cursor-based)

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

With no annotations, the description carries the full burden. It discloses that the tool follows pagination until complete, that initial syncs may return empty for new Items, and that a webhook signals readiness. It does not mention auth, rate limits, or side effects, but as a sync operation the behavior is sufficiently disclosed for typical use.

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?

Two sentences that are dense with information and front-load the core behavior. No wasted words; the key behavioral details and usage notes are efficiently delivered.

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?

The description covers the main aspects an agent needs: pagination behavior, cursor usage, and the initial-empty-Item caveat. It does not explicitly describe the return shape (e.g., contains transactions and next_cursor), but given the tool's name and context, this is a minor omission. Overall, it is sufficiently complete for a sync tool.

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 coverage is 100%, so the baseline is 3. The description adds value by clarifying the cursor parameter ('Omit for the initial full sync') and describing max_pages as a 'Safety cap', which supplements the schema. This lifts it above baseline without being redundant.

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 it calls /transactions/sync and follows has_more until complete, providing a consistent snapshot. It distinguishes itself from sibling tools by focusing on transaction syncing and incremental updates via cursor, making its purpose unambiguous.

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 explains when to use it (initial full sync vs. subsequent incremental syncs with a cursor) and notes that a brand-new Item may return zero transactions initially, suggesting waiting for a webhook or retrying. It provides clear context for usage but does not explicitly mention alternatives, though no sibling directly competes.

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