Criar ou atualizar ticket

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states it creates/updates tickets, but it does not explain side effects: whether updates overwrite all fields or only provided ones, whether creation requires specific fields, or what the response contains. Since it is a mutation tool (upsert), the lack of these details is a significant transparency gap.

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 sentences with no fluff. It front-loads the core purpose ('cria/atualiza ticket'), lists relevant types, and gives a key usage hint. Every word adds value, making it a model of efficient writing.

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 complexity (9 parameters, no required fields, low schema coverage, no output schema, and no annotations), the description is markedly incomplete. It does not specify what fields are necessary for creation, what happens on update (e.g., partial or full overwrite), or what the tool returns. An agent would have to open the schema and still miss the behavioral semantics. This is insufficient for a mutation tool with such a parameter surface.

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 44%, so the description needs to compensate for the missing parameter explanations. It adds clarity for 'id' (format KEY-N, use for status update) and implicitly mentions the 'type' via the list of ticket types, but it does not explain other parameters like 'status', 'priority', 'title', or 'description'. It partially compensates but leaves many parameters undocumented.

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 tool creates/updates tickets and lists the ticket types (story, bug, task, spike, epic). However, it does not explicitly differentiate itself from the sibling tool 'work_upsert_task', which could lead to confusion. The verb+resource is clear, but the lack of distinction from a closely named sibling prevents a perfect score.

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 instruction 'Passe id para atualizar status' provides some guidance on when to pass an id (update) versus when to create, implying the conditional usage. However, it does not mention any alternative tools or when NOT to use this tool, leaving the routing between work_upsert_ticket and work_upsert_task ambiguous. There is no explicit exclusions or alternatives, so it is adequate but not complete.

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