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

Annotations already declare a non-read-only, non-destructive, open-world mutation, so the bar is lower; the description earns credit by disclosing the social side effect ("changes are visible to the user's team") and the need to confirm first. It also warns that the description parameter replaces the entire body, which is meaningful destructive-in-practice context not conveyed by destructiveHint=false.

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 sentence, front-loaded with the action verb, with the three capabilities listed compactly and the confirmation caution placed at the end where it is most visible. No redundant restatement of the title or name.

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 an open-world mutation with no output schema, the description covers the important safety and sourcing context. However, the schema shows zero required parameters, and the description never says what happens if the agent calls it with no fields set or how partial updates behave — a real ambiguity for a write 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?

Schema coverage is 100%, so the baseline is 3. The description adds modest value by tying status to names returned by list_tickets and framing description as a whole replacement, but it does not explain whether omitted fields stay untouched or whether at least one field must be supplied.

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+resource (change a Jira/ClickUp ticket) and enumerates the three concrete operations: status move, due date set, description replace. It is clearly distinguishable from siblings like get_ticket, comment_ticket, and list_tickets.

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 real prerequisite ("use a status name shown by list_tickets") and a procedural caution ("confirm with the user first"). It does not explicitly exclude alternatives such as comment_ticket when the user wants to add a note rather than change fields, so it stops short of full when/when-not guidance.

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