find_or_create_customer

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

With no annotations provided, the description carries the full burden. It discloses the search order (name then phone), that it proposes creation, and implies auto-creation is controlled by the create_if_not_found parameter. However, it does not specify behavior for edge cases like multiple matches or when creation is declined.

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 concise (three sentences), front-loaded with the core purpose, and includes a practical example. Every sentence earns its place with no fluff.

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 description covers purpose, usage trigger, search strategy, and an example, which is fairly complete for a find-or-create tool. However, it lacks details on what happens when the customer is not found and create_if_not_found is false or how the result is returned, especially since there is no output schema. Still, the core behavior is well explained.

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 baseline is 3. The description adds value by specifying that name and mobile_no are used in a particular search order (name first, then phone), which enriches the semantic meaning beyond the schema's simple field descriptions.

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 finds an existing customer or creates a new one, with a specific verb and resource. It also distinguishes this tool by providing usage context with create_sale, making its purpose unambiguous.

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?

Explicitly instructs to use before create_sale when the user mentions a customer name, and provides a clear search strategy (by name then phone) before proposing creation. This gives concrete when-to-use guidance and differentiates from alternatives.

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