monzo_get_balance

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

No annotations exist, so description carries full burden. It notes the side effect of recording a balance snapshot, which is valuable. However, it doesn't disclose authentication needs, rate limits, or whether it's safe/read-only. The snapshot side effect is mentioned but not detailed.

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?

Three sentences with bullet point for argument. No redundancy. Every sentence adds value. Extremely concise and clear.

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?

An output schema exists (not shown but indicated), so return values are documented externally. Description mentions returns and side effect. For a simple read tool with one parameter, this is fully complete.

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 0% description coverage, but the tool description explains account_type as 'personal' or 'joint' with default 'personal'. This adds meaning beyond the raw schema, though it could be more precise (e.g., listing exact values as enum). Given only one parameter, it's sufficient.

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?

Description clearly states 'Get current balance for a Monzo account' and specifies return values (balance, spend today, currency) and side effect (records snapshot). It distinguishes from siblings like monzo_list_accounts or monzo_list_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 or not use this tool. It doesn't mention alternatives or prerequisites. Usage is implied by the purpose description but lacks clear contextual direction.

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