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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive write, and the description reinforces that with concrete refusal preconditions and a per-role concurrency limit, which is real added context. It stops short of saying what side effect the call produces on the ticket (status change, assignment, notifications), which would complete the behavioral picture.

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?

Two tight sentences with no filler: the primary action and extension come first, followed by the failure conditions. Every clause carries operational meaning.

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 one-parameter, no-output-schema tool with annotations present, the definition covers preconditions and limits well. The only meaningful gap is that it does not state the resulting state change or what the agent gets back on success.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains the ticket key format ('LG-12' or its id). The description adds nothing beyond that, which is the expected baseline for a fully documented single parameter.

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 names a specific verb and resource ('Start a ticket') and immediately extends it to a distinct second case ('resume it after block_ticket, ask_decision or a QA return'), so an agent knows both the action and the state transitions it covers. This is clearly separable from siblings like block_ticket, ask_decision, and get_ticket.

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 gives explicit when-to-use guidance (after a block, a decision request, or a QA return) plus explicit when-not conditions: refused if the ticket belongs to someone else, is already started, or the caller is at their concurrency limit. The worker constraint ('one ticket in progress at a time') removes the main ambiguity an agent would hit.

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