monzo_spending

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

Discloses auto-sync behavior if cache is stale, which is a key behavioral trait, but lacks details on sync blocking, state changes, or return format fallback. Without annotations, the description adds moderate 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?

Reasonably concise with front-loaded purpose and structured parameter list. The auto-sync note could be integrated more seamlessly, but no redundancy.

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 main use case and parameters sufficiently; output schema likely handles return values. Lacks explanation of category summary structure or caching details, but adequate for the tool's 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?

Schema has no descriptions (0% coverage), but the description adds clear semantics for all 4 parameters: month format, category examples, account_type valid values, and detail boolean purpose, significantly aiding agent usage.

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 analyzes spending from cached Monzo transactions, using the specific verb 'analyse' and resource 'Monzo transactions', which distinguishes from sibling tools like monzo_list_transactions or monzo_search_transactions.

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?

No explicit guidance on when to use this tool versus alternatives like monzo_list_transactions or monzo_sync. The description mentions auto-syncing, but does not clarify scenarios where raw or synced data is needed.

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