sync_simplefin

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

Discloses read-only nature against SimpleFIN, idempotent upsert, reading env var, and return value (counts and warnings). Lacks details on error handling or rate limits, but generally transparent.

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?

Five sentences, front-loaded with main action, each sentence adds value with no redundancy or fluff.

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?

No output schema, but description mentions return counts and warnings. Covers main parameters and behavior. Could elaborate on db_path and end_date, but overall sufficient for a sync tool with 5 params.

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 0%, but description explains start_date, incremental, and lookback_days behavior (e.g., incremental reset when start_date given). However, end_date and db_path are not described. Partially compensates for missing 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 clearly states it pulls live accounts, balances, and transactions from SimpleFIN into the DB, using specific verb and resource. It distinguishes from sibling tools like sync_todoist or list_statement_cycles.

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?

Explains when to use incremental vs start_date, mentions SimpleFIN's 90-day cap, and that incremental resumes from last sync. Does not explicitly mention when not to use or alternatives, but provides clear context for choosing parameters.

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