monzo_sync

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

With no annotations, describes key behaviors: fetches up to 11 months, automatic pagination, deduplication, and SCA constraint. Lacks mention of write behavior to local cache but is clear on sync operation.

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?

Concise with intro and bulleted args. No fluff, every sentence adds value. Well-structured for quick parsing.

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?

Covers sync behavior, parameters, and constraints. Output schema exists so return values are handled. Might be missing a note on caching effects but overall sufficient for complexity.

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?

Adds significant meaning beyond schema: explains account_type values and since parameter format, including ISO date/datetime, override behavior, and SCA window restriction. 0% schema coverage so description is essential.

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?

Clearly states syncing transactions, balances, and pots from Monzo API to local cache, with specific verb and resource. Differentiates from sibling tools like monzo_list_transactions which do not sync.

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 explicit context on when to use: handles pagination, deduplication, and fallback behavior. Mentions SCA window and parameter usage. Does not explicitly state alternatives but implies use for bulk sync vs. simple queries.

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