add_expense

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that an expense is added. It does not mention validation, required fields, idempotency, date handling, or any side effects beyond the creation itself, which is thin for a write operation.

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, front-loaded sentence with no filler words. It is concise and easy to parse, though the phrase 'to the tracker' adds little substance and the description could have used the space to communicate more useful details.

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 tool with no annotations, five parameters, and zero schema descriptions, the description is incomplete. It omits what the required fields represent, how dates should be formatted, and how this creation compares to recurring expense creation; an output schema does not compensate for these calling-semantics gaps.

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%, and the description provides no compensation by explaining the meaning of amount, category, subcategory, or expense_date. The agent gets no additional semantic value beyond the parameter names in 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 a specific verb and resource: 'Add a new expense to the tracker.' However, it does not explicitly distinguish this from the sibling add_recurring_expense, leaving whether this is a one-time or recurring expense to be inferred from the tool name rather than the description.

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 gives no indication of when to use this tool versus update_expense or add_recurring_expense. There are no preconditions, exclusions, or alternative routing, so an agent must rely entirely on tool names to make the correct selection.

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