add_expense

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action of adding an entry, but gives no information about side effects, required fields, validation rules, permissions, or return values. For a mutation tool, this is a significant gap.

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 a single sentence with no unnecessary words, making it concise. However, it is too terse to provide meaningful guidance; key information about parameters and usage is absent. It is not a tautology, but it under-specifies for the tool's complexity.

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 5 parameters (3 required), no output schema, and no annotations, the description is severely incomplete. It provides no parameter semantics, no return value expectations, no usage context, and no behavioral caveats. The tool is functionally a black box beyond its name.

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?

The input schema has 5 parameters with 0% description coverage, and the tool description does not mention any parameter meanings. It only says 'new expense entry', which adds no value in explaining what date, amount, category, note, or subcategory represent. The description entirely fails to compensate for the schema's lack of documentation.

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 'Add a new expense entry to the database' uses a specific verb (Add) and resource (expense entry), clearly distinguishing this from sibling tools list_expenses and summarize. It unambiguously identifies the action without ambiguity.

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 wording 'Add a new expense entry' implies this tool is for creating new expense records. However, it provides no explicit guidance on when to use it vs. alternatives, nor does it mention any prerequisites or exclusions. Usage is implied rather than explicitly stated.

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