tomticket_update_customer

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

With no annotations, the description carries the burden and does add behavioral context: 'altera producao' warns of production impact and 'Propriedade vazia e ignorada' clarifies empty-field semantics. However, it omits other important behavioral traits such as irreversibility, permissions, or what happens when conflicting fields are supplied.

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 and front-loaded with the most important warning ('ATENCAO: altera producao') before stating the action. Every sentence earns its place with no filler.

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?

Given 12 parameters, low schema coverage, no annotations, and no output schema, this description is far from complete. It explains one behavioral nuance but does not provide enough context for an agent to confidently invoke the tool with correct parameters or understand response behavior.

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 33%, and the description does not compensate for the undocumented parameters. The only parameter-related insight is that empty properties are ignored, which adds some value but leaves many fields (name, email, phone, language, password, portfolio_id, etc.) without meaningful explanation.

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 verb and resource: 'Atualiza dados do cliente' (updates customer data). This distinguishes it from sibling list/create/get tools, though it doesn't explicitly contrast it with tomticket_create_customer or other update tools.

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. It warns that it alters production, which implies caution, but does not state prerequisites, exclusions, or conditions that would route an agent to a sibling tool.

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