tomticket_create_customer

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

With no annotations provided, the description carries the behavioral disclosure burden. The explicit warning 'ATENCAO: altera producao' is valuable and discloses that this is a production-mutating operation. However, it does not mention error behavior, idempotency, permission requirements, or consequences beyond the generic warning.

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 extremely concise: a production-change warning followed by a clear statement of purpose. Every word earns its place and the most important operational caveat is front-loaded.

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?

This is a write operation with 10 parameters, no annotations, and no output schema, yet the description only offers a one-line purpose and generic production warning. It does not explain required fields, validation rules, side effects, or what a successful response looks like, so it is not sufficiently complete for reliable invocation.

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 description coverage is only 30%, and the description adds no parameter-level meaning. The schema documents language and customer_id, but the other eight parameters remain unexplained, and the description does not compensate for this gap.

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 verb 'Cria' (creates) and the resource 'cliente' (customer), making the tool's purpose unambiguous. This differentiates it from sibling tools like list_customers, get_customer, 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?

The description provides no guidance on when to use this tool versus alternatives such as update_customer or create_organization. There are no prerequisites, exclusions, or conditions mentioned, leaving the agent to infer usage solely from the tool name.

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