create_customer

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

Annotations already indicate destructiveHint: true, and the description adds a warning emoji and 'Confirmar con usuario', reinforcing the destructive nature. However, it does not disclose additional behavioral traits such as required permissions, irreversibility, or side effects beyond creation.

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 short and front-loads the warning with a bullet-like structure for parameter conditions. It is efficient, but the mixed language (Spanish) and lack of formal structure reduce clarity slightly.

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?

For a tool with 21 parameters (6 required) and an output schema (not shown), the description covers the conditional business_type logic and some enum values but fails to explain the purpose of required fields like region, address, or postal_code. The return value is not mentioned, though the output schema may compensate.

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?

Despite 0% schema description coverage, the description explains conditional requirements for business_type (name/surname_1 vs business_name) and lists allowed values for default_invoice_language and tax_id_type. This adds significant meaning beyond the schema, though some required parameters like region, address, etc. are not explained.

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 'Crea un cliente' (creates a customer) and includes a warning to confirm with the user. It distinguishes from sibling tools like create_provider or create_invoice. However, the title is null and the description is in Spanish, which may reduce clarity for non-Spanish agents.

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 includes 'Confirmar con usuario', suggesting the tool should only be used after user confirmation, but provides no explicit guidance on when to use this tool versus alternatives like update_customer or delete_customer. There is no context for selecting this tool over siblings.

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