monzo_sync

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

With no annotations, the description carries full burden. It discloses automatic pagination and deduplication, fetch strategy, and account_type behavior. However, it does not mention side effects (e.g., cache overwrite) or auth requirements, which would enhance transparency.

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 compact and well-structured, with a clear purpose sentence followed by detailed behavior in bullet points. No unnecessary words or repetition. Every sentence adds value.

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 the tool's single parameter and no annotations, the description covers purpose, parameters, and behavior adequately. It lacks mention of error conditions or prerequisites (e.g., authenticated Monzo API), but an output schema exists so return details are not required. Minor gaps prevent a perfect score.

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 description adds significant meaning beyond the schema: it specifies valid values for account_type ('personal', 'joint', or None) and explains the effect of each. This compensates for 0% schema description coverage.

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 the tool's purpose: 'Sync transactions, balances, and pots from the Monzo API into the local cache.' It uses a specific verb and resource, and distinguishes itself from sibling tools like monzo_list_transactions or monzo_get_balance by focusing on bulk syncing.

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 provides usage context by explaining fetch boundaries (11 months or 90 days) and automatic handling of pagination and deduplication. It implies use for initial or bulk sync but does not explicitly compare to siblings or state when not to use it.

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