Lunch Money MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't specify whether this is permanent/irreversible, requires specific permissions, has side effects (e.g., cascading deletions), or returns confirmation data. This is inadequate for a destructive operation with zero annotation coverage.

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 extremely concise (4 words) and front-loaded with the essential action and target. Every word earns its place with zero redundancy or unnecessary elaboration. This is optimal for a simple tool with minimal parameters.

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?

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context: what happens after deletion (confirmation message? error handling?), whether the operation is idempotent, or what permissions are required. The agent lacks sufficient information to use this tool safely and effectively.

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 description coverage is 0%, but the description adds minimal parameter context by specifying 'by ID'. However, it doesn't explain what 'ID' refers to (transaction identifier format/source) or provide examples. With only one parameter and the schema defining it as a positive integer, the description adds marginal 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 the action ('Delete') and target resource ('a transaction by ID'), making the purpose immediately understandable. It distinguishes from sibling tools like 'deleteAsset' or 'deleteBudget' by specifying the transaction resource type. However, it doesn't explicitly mention what 'delete' entails (permanent removal vs soft delete).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., transaction must exist), when-not-to-use scenarios, or relationships with sibling tools like 'updateTransaction' or 'getTransactions'. The agent must infer usage from the tool name alone.

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