monzo_sync

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

Without annotations, the description shoulders the transparency burden. It adequately discloses pagination, auth-hold deduplication, and sync window behavior, but could mention side effects like overwriting existing cached data.

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?

The description is well-structured: a concise front-loaded purpose sentence, a paragraph with behavioral details, and a clean Args section. No unnecessary verbiage.

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 syncing behavior, history length, fallback logic, pagination, and dedup. It doesn't mention output format, but an output schema exists, reducing that need. Slight gap: not specifying that it updates the local cache.

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 single parameter account_type is described with examples ('personal', 'joint', None) in the docstring, adding meaning beyond the schema's minimal type info. However, valid values are not precisely enumerated.

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 uses a specific verb ('sync') and resource ('transactions, balances, and pots'), clearly distinguishing it from sibling tools like monzo_get_balance or monzo_list_transactions which are read-only queries.

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 implies this is for initial sync or cache refresh by mentioning history length and fallback, but does not explicitly state when to use this versus alternative read tools, nor provide clear exclusions.

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