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

Beyond the annotations, the description discloses real behavioral consequences: fixed closes the ticket stamped as confirmed, still_broken returns it red to the queue with the message as the reason, and no re-filing occurs. It also flags the still_broken message requirement, which the schema does not enforce. No contradiction with annotations.

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 front-loaded with the core action and is dense with useful guidance, but it is long and contains stylistic asides such as 'that line is the most useful one on the whole list.' Overall it stays on-topic and every sentence supports correct usage.

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 3-parameter tool with no output schema, the description covers all ticket states, both verdict semantics, the required message condition, and the relationship to gap_check. An agent has enough information to invoke the tool correctly in every branch.

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 coverage is 100%, so the baseline is 3, but the description adds significant meaning: message becomes mandatory for still_broken, verdict is constrained to pending tickets, and omitting verdict changes the operation to a plain thread addition. This goes beyond the schema's individual property descriptions.

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 a clear verb and resource ('ANSWER ON YOUR TICKET') and immediately distinguishes three concrete behaviors: close as fixed, send back as still_broken, or just add a message. It also ties 'fixed' to running the verify line from gap_check, separating this tool from report_gap and gap_check.

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'), what happens on open or closed tickets, and when to leave verdict off. It also names the prerequisite for a verdict by referencing gap_check's verify line.

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