add_monthly

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

No annotations are provided, so the description carries full burden. It explains the batch 'upsert' behavior for a single period, which implies creation/update, but doesn't disclose whether it replaces or appends existing period data, or mention authorization or rate limits. Some transparency but gaps remain.

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 front-loaded with the core purpose and includes necessary detail on valid categories and workflow. While lengthy, every sentence serves a purpose for correct tool invocation. Could be slightly more concise but remains efficient.

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 2 required and 2 optional parameters with no output schema, the description covers the main use case, data constraints, and post-call action (call report). It lacks error handling or behavior on duplicate periods, but is sufficiently complete for the intended monthly settlement task.

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 50%, but the description adds significant value by listing all valid category strings and their required sub_type (e.g., 'assets: cash, savings, ...'). This compensates for the schema's free-text sub_type and category fields, ensuring correct parameter usage beyond schema definitions.

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 'Batch upsert balance and flow entries for a single period in one call', specifying the verb (batch upsert) and resource (balance and flow entries). It distinguishes from siblings by highlighting it as the primary tool for month-end settlement, unlike individual add_balance/add_flow tools.

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?

Provides explicit step-by-step instructions for when to use: 'When the user says "결산", "월말 결산", "month-end closing", or "record this month"' and outlines the required workflow (ask for categories, confirm numbers, call tool once). It also lists valid categories and sub_types, preventing misuse.

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