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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), so the bar is lower. The description still adds real value: optimistic-concurrency protection via last updatedAt, and an auth caveat that application roles do not grant support permissions.

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?

Three tight sentences, front-loaded with the action, followed by the concurrency requirement and the permission caveat. Every sentence carries information; 'change' is the only slightly loose term.

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 9-parameter mutation tool, the description covers concurrency and authorization but is thin on the parameters themselves. The output schema exists, so return values need no explanation, and annotations carry the safety profile, leaving the parameter gap as the main shortfall.

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 only 11% (just widgetId documented) across 9 params, so the description must compensate. It partially does by naming the field groups it operates on (assignee, priority, tags, status) and the updatedAt semantics, but leaves team, workId, and the enum value sets undocumented.

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?

States a specific verb set and resource: 'Assign, prioritize, tag or change a support ticket.' An agent immediately knows this mutates ticket fields. It does not, however, distinguish itself from close siblings like support_reply_ticket or support_save_work, so the boundary is left implicit.

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?

No explicit when-to-use guidance or routing to alternatives is given, despite five sibling support_* tools (get, list, reply, save). The only operational hint is the updatedAt concurrency note, which is behavioral rather than a selection rule.

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