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

Annotations only signal mutation and non-destructiveness; the description goes far beyond by explaining concrete consequences: fixed closes the ticket 'stamped as confirmed by the reporter,' still_broken sends it 'back onto the queue, red, with your sentence as the reason it bounced — no re-filing.' It also discloses the behavior on non-pending tickets and the message requirement, all of which an agent needs to predict effects.

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 core instruction is front-loaded in the first line, and every behavioral rule earns its place. However, the prose is somewhat embellished ('that line is the most useful one on the whole list') and could be tightened without losing information, so it is not maximally concise.

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?

The description covers the full decision space: pending vs non-pending behavior, both verdict semantics, the still_broken message requirement, and the no-personal-brief styling rule. With annotations covering the safety profile and no output schema needed for this simple action, nothing essential is missing for an agent to invoke it correctly.

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?

The schema already covers all three parameters, so the baseline is 3, but the description adds real operational meaning: verdict values are tied to specific outcomes, message is mandatory for still_broken, and id uses the pg_… prefix. It clarifies when to omit verdict entirely, which is not obvious from the schema alone.

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 opens with 'ANSWER ON YOUR TICKET' and immediately specifies the two verdict-driven actions: close it or send it back. It clearly identifies the resource (ticket) and the verb (reply/decide), and distinguishes this tool from filing by referencing 'Same rule as filing' and the gap_check verify workflow. The purpose is unmistakable and well-differentiated.

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 explicitly states when a verdict applies ('only applies to a pending ticket') and when it does not ('on an open or closed one your message lands in the thread for a person to read instead'). It also instructs to leave verdict off to simply add to the thread and requires a message for still_broken. This is clear, concrete when-to-use and when-not-to-use guidance.

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