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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description adds real value beyond them: it warns that changes are visible to the user's team and instructs confirmation before acting. It also discloses that the description field is a wholesale replacement, which matters for an agent about to overwrite existing text. It does not describe the return value or partial-failure behavior, keeping it below 5.

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 sentences, front-loaded with the core action and its options, followed by the safety caveat that should govern invocation. No redundant or filler wording.

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 7-parameter mutation tool with zero required parameters and no output schema, the description should clarify which parameter combinations are valid and what a call returns. It covers the three headline operations but never mentions assignee, nor that account_id must accompany ticket_id, leaving the agent to infer composition from the schema alone.

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 100%, so every parameter is already documented in structured data, and the description adds little beyond restating status/due_date/description. It does supply a useful convention ('status name shown by list_tickets') that ties parameters to a sibling tool. It says nothing about assignee, ticket_id/account_id pairing, or conversation_id, but the schema handles those.

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 (change) and resource (Jira/ClickUp ticket) and enumerates three concrete operations: status move, due date, and description replacement. It is clearly distinguishable from siblings like create_ticket and get_ticket. However, it omits the assignee operation that the schema supports, so the stated scope is narrower than the tool's actual capability.

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 a concrete prerequisite (use a status name shown by list_tickets) and a workflow instruction (confirm with the user first), which directly shapes correct invocation. It stops short of naming when to prefer a sibling such as comment_ticket for pure commentary, but the mutation context is clear.

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