monzo_search_transactions

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

No annotations provided, so description carries full burden. Discloses auto-sync behavior, case-insensitive partial match, and which fields are searched. No mention of rate limits or side effects, but adequate for a search tool.

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?

Purpose front-loaded, Args section clear. Slight redundancy in mentioning 'case-insensitive partial match' twice. Overall concise with minimal wasted text.

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 search behavior, matched fields, auto-sync, date formats, default limit. With output schema present, no need to explain return structure. Adequate for a 5-param tool with 1 required param.

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 adds an Args section with explanations for each parameter: query, account_type, since, before, limit. Adds meaning beyond schema types (e.g., 'personal' or 'joint' for account_type, ISO format for dates).

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 'Search cached transactions' with specific search fields (merchant, counterparty, description, notes). This distinguishes it from siblings like monzo_list_transactions (which likely lists all transactions) and monzo_sync (data 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 usage context: auto-syncs if cache stale, case-insensitive partial match, and specifies matching fields. Does not explicitly state when not to use or alternatives, but context is clear enough.

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