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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the definition of each bucket (OVERDUE = ended before today, UNPLANNED = no dates) and the fact that results are grouped rather than a flat list. It omits ordering within a group and whether counts/totals are returned.

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?

It is a single front-loaded sentence that opens with the user-facing question and then supplies the bucket taxonomy, with no filler. The dense em-dash-and-parenthetical list is information-rich but slightly harder to scan than a short bulleted structure would be.

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 two-parameter, zero-required, read-only list tool with no output schema, the description supplies scope, bucket semantics, and defaults, which is nearly everything needed to invoke it correctly. The remaining gap is what each ticket entry contains and how results are ordered or paginated across groups.

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 a 3 is the floor, but the description goes beyond the enum list by explaining what each bucket actually means (e.g. THIS_WEEK = lies in this week, OVERDUE = ended before today) and restating the default of OVERDUE + THIS_WEEK. It does not clarify the per-group nature of `limit`, though the schema already covers that.

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 resource (open tickets assigned to the user) and a specific grouping model (the Workload page's six buckets), so an agent knows exactly what comes back. It does not explicitly contrast with the closest siblings (search_tickets, my_week), so it stops short of full sibling differentiation.

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?

"What's on the user's plate" plus "assigned to them" implies the usage context, and the stated default (overdue + this week) tells the agent what happens if it passes nothing. However, there is no explicit when-to-use-this-versus-my_week or search_tickets guidance and no exclusions (e.g. closed tickets), so guidance is only implied.

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