add_customer

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

Annotations already disclose that this is not read-only and not idempotent, so the description carries a light behavioral load. It adds context by naming the destination ('Chirak store contacts directory') and the notion of a new entry, but does not disclose side effects like duplicate handling or authorization requirements.

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 well-structured sentence that front-loads the core action. No filler, no redundancy, and every word counts.

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?

With a fully described input schema, an output schema present, and annotations covering the mutation/idempotence profile, an agent has sufficient information to invoke the tool correctly. Nothing critical is missing for this straightforward create operation.

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 coverage is 100%, so all seven parameters are individually described with full meaning, including the string list for channel. The description adds no additional parameter-level information, which is acceptable at this coverage level.

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 uses a clear verb ('Add'), a specific resource ('a new customer'), and a definitive scope ('Chirak store contacts directory'). It unambiguously distinguishes itself from sibling tools like update_customer, delete_customer, and list_customers through the concept of creating a new record.

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 states the fundamental action ('Add a new customer') and implies it is for new records, but it doesn't explicitly reference alternative tools such as update_customer for existing customers or list_customers for lookups. No exclusions or when-not-to-use guidance is provided beyond the inherent meaning of 'new'.

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