Create Customer

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

The description adds context that no merchant ID is needed and that the tool is always connected to the API. However, it incorrectly states that email is optional, while the schema requires email, misrepresenting the required fields. This misleading behavioral guidance lowers the score.

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 at three sentences and front-loads the main action. It contains practical guidance but is marred by the inaccuracy about email being optional.

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 has 15 parameters, no output schema, and no schema descriptions, so the description is the only source of context. It lacks details on most parameters, return values, or constraints, and the email contradiction makes it incomplete.

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?

With 0% schema description coverage, the description must explain the parameters. It only mentions name as the minimum requirement and labels email and others as optional, which is factually wrong for email. No semantics are provided for document, address fields, metadata, or documentType.

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 states a clear action: 'Cria um cliente na API' (creates a customer in the API), with a specific verb and resource. This distinguishes it from sibling tools like get_customer, list_customers, and update_customer.

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?

It gives a direct trigger example: if the user says 'cria cliente chamado Jorge', call with name='Jorge'. It also instructs not to ask about API vs panel, indicating it's always the API path. However, it doesn't mention alternatives like update_customer or when not to use this tool.

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