update_ticket

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

With no annotations, the description carries the behavioral burden and does so meaningfully: it discloses partial-update/PATCH behavior, that tags replace the full list, that ticket_id is the internal ID, and null semantics for optional fields. It does not mention permissions or side effects, but the disclosed mutation semantics are substantial.

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 semantics and common use cases, then follows a consistent, compact Args list. It is longer than average but every line earns its place given 11 parameters and zero schema descriptions to rely on.

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 tool's complexity, output schema, and absent annotations, the description is essentially complete: it explains what the tool does, when to use it, PATCH behavior, field formats, replacement semantics, and ID pitfalls. The only minor blemish is the ambiguous 'pass empty string to unassign? Use null' note, which does not undermine overall completeness.

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 0%, so the description must compensate, and it largely does: every parameter is listed with added meaning — valid status/priority/severity values, ISO date format, title length limit, tags replacement behavior, and the internal vs display ID distinction. A few entries are low-value ('New description'), but the overall coverage is excellent.

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 specific verb and resource: 'Update a service-level ticket', and immediately clarifies PATCH semantics and common use cases (status transitions, reassignment, priority bumps). This clearly distinguishes it from sibling creation, commenting, and linking tools.

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 to use the tool: status transitions, reassignment, priority bumps, etc. It does not explicitly mention alternatives or exclusions, but the use cases and PATCH semantics are enough to guide selection.

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