tomticket_create_ticket

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

With no annotations provided, the description takes on the behavioral disclosure burden. It explicitly warns 'ATENCAO: altera producao' (changes production), which is a meaningful and useful alert about mutation impact. However, it does not disclose other behavioral aspects such as required permissions, side effects, or what happens on success.

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: two short sentences. The production warning is front-loaded and the purpose is stated directly. Every word earns its place with no redundancy.

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 9-parameter creation tool with no annotations and no output schema, a single sentence is insufficient. It does not explain key required inputs, prerequisites, or what the tool returns after creation. The moderate schema coverage does not overcome the overall lack of context.

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 56%, and the description itself adds no parameter-level meaning. Required parameters like department_id, subject, and message have no schema descriptions and are not clarified in the description. Only the schema documents customer_id, priority, attachments, custom_fields, and customer_id_type.

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 specific verb and resource: 'Cria um novo chamado' (creates a new ticket). This clearly distinguishes it from sibling creation tools like create_customer, create_organization, and create_article, all of which target different resources.

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?

Usage is implied by the description: use this when a new ticket needs to be created. However, there is no explicit guidance on when not to use it or how it compares to alternatives like reply_ticket, transfer_ticket, or finish_ticket.

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