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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds little beyond that: nothing about partial extraction, missing fields, or confidence. It does implicitly confirm the tool works purely on supplied text rather than fetching anything.

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?

One front-loaded sentence with no filler, and the field list is packed into a verb phrase rather than a bulleted afterthought. It could be tightened slightly, but nothing is redundant.

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?

No output schema exists, so the description carries the burden of describing the return, and the field list does that reasonably well. However, it never says what shape the response takes—structured object versus free text—or what happens when a field is absent from the ticket, which matters for an extraction 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?

There is a single parameter with 100% schema description coverage, so the schema already documents it. The one value-add from the description is "plain text" and "one-call ticket," which hints the input should be raw email body text rather than HTML, but it never states this explicitly or warns about attachments or HTML markup.

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 action ("pull ... out of") and enumerates the fields returned: ticket number, type, dates, excavator, address, work area, coordinates, member utilities. An agent can tell this is an extractor, not a calculator like the dig-clock sibling. It stops short of explicitly differentiating itself from siblings such as dig_clock_811, which likely consumes the same ticket text.

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?

Usage is only implied: "out of the plain text of a one-call ticket" signals the input must be raw ticket text, which is a mild precondition. There is no statement about when to call this versus a sibling, no mention of error behavior for unparseable or truncated tickets, and no indication of whether to use it before or after a deadline calculation.

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