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

Annotations include readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds context by specifying partial update behavior and bulk support for certain fields. It does not contradict annotations. The description explicitly mentions the bulk fields, which is a behavioral trait beyond what annotations provide. It doesn't mention error conditions or permissions, but for an update tool with no destructive hint, this is adequate.

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 and well-structured. It has a clear main sentence, a key usage tip, and a separate paragraph for bulk support. Every sentence adds value. No fluff.

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 the tool has 21 parameters, no output schema, and minimal annotations, the description provides essential information: what to update, how to specify stage/responsible, and bulk capability. It could add more about the response format or error handling, but since there's no output schema, the agent would need to infer that from other tools or documentation. The description covers the critical aspects sufficiently for a complex update tool.

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 0%, so the description must compensate. The description explains the semantics of key parameters: stage_id for moving stages, responsible_id for transferring responsibility, and lists all the bulk fields (client_ids, desk_ids, etc.). It also clarifies that only fields to be changed should be sent, which helps with the 21 parameters. However, it doesn't explain every parameter, but the list of common ones is sufficient for an agent to infer the rest.

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 'Atualiza um chamado existente' (updates an existing ticket), which is a specific verb+resource combination. It distinguishes itself from sibling tools like tiflux_create_ticket, tiflux_close_ticket, and tiflux_cancel_ticket by focusing on updates. The scope is clear: it updates an existing ticket and supports partial updates ('Envie só os campos a alterar').

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 provides clear guidance on when to use this tool: to update an existing ticket, with explicit instructions on how to move stages and transfer responsibility. It implicitly differentiates from creation and lifecycle tools by saying 'existing ticket.' However, it does not explicitly mention when NOT to use it or name alternative tools for cases like closing or canceling, but the context of siblings makes this clear enough.

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