monzo_spending

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

With no annotations, the description discloses the auto-sync behavior and the effect of the detail parameter. It is a read operation and no side effects are mentioned, which is appropriate. Could specify if sync is blocking.

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 concise, uses a structured Args section, and includes the auto-sync note upfront. No redundant sentences.

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 presence of an output schema, the description covers purpose, parameters, and behavioral aspects. It is complete for a spending analysis tool.

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 the description adds full meaning to each parameter: month format, category examples, account_type options, and detail boolean. Adds value beyond the schema.

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 'Analyse spending from cached Monzo transactions', specifying the verb and resource. It implicitly distinguishes from sibling tools like monzo_list_transactions by focusing on aggregated analysis.

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 indicates when to use ('analyse spending') and mentions auto-sync behavior. It provides filtering options but does not explicitly contrast with siblings or state when not to use.

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