update_ticket

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context with the "[policy: require_approval]" gate, which is not in any structured field. However, it never explains what happens to fields left unset (empty-string defaults suggest 'no change' but this is unstated) or how the approval gate manifests in the response.

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?

A single front-loaded sentence with the policy tag leading and the mutable fields plus their value domains packed in. No filler, no restatement of the title.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. What remains missing for a mutation gated by policy is the operational meaning of require_approval and whether omitted fields preserve or clear existing values. Adequate but with real gaps for a state-changing 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?

With 0% schema description coverage and no enums in the schema, the description carries the full parameter burden and does real work: it supplies the legal values open|in_progress|closed and P1-P4, and 'and/or' signals that fields are optional partial updates. It stops short on assignee (user ID vs email vs name) and gives no meaning to ticket_id.

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?

Specific verb plus resource ("Change a ticket's status... priority... assignee") with the allowed values enumerated inline, so an agent immediately knows what the tool mutates. It is clearly not a read tool like get_ticket or search_tickets, though it never explicitly names those siblings as alternatives.

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?

The description implies when to use it (when a ticket's status, priority, or assignee must change) but offers no explicit comparison to siblings such as add_comment or approval_status. The require_approval policy tag hints at a prerequisite, yet the description never states whether the agent must call approval_status first or what to do if approval is pending.

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