ecount_save_customer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. '거래처를 등록한다' implies a write operation (creating a customer), but there's no information about duplicate handling, required permissions, side effects, or response format. The manual reference is a pointer, not an actual disclosure.

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, concise sentence that conveys the core purpose and includes a manual reference for details. Every word earns its place; no fluff or redundancy.

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?

The tool is a mutation (write) operation with no annotations and a minimal description. It doesn't address potential complexities like duplicate customers or ERP-specific settings, leaving the AI agent under-informed. The output schema exists but is not visible, and the description does not compensate for the lack of behavioral context.

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 schema description covers 100% of the only parameter (customers), detailing required and optional keys. The tool description itself adds no parameter-level information, but since schema coverage is high, a baseline of 3 is appropriate.

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 tool's function: '거래처를 등록한다' (register a customer), which is a specific verb and resource, and is distinct from sibling tools like ecount_save_invoice or ecount_web_export_tax_invoices. The manual reference adds credibility and precision.

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 this tool versus alternatives. While it's obvious that it's for customer registration, the description doesn't mention scenarios, prerequisites, or exclusions. The manual reference could imply more details, but it's not stated in the description itself.

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