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

With readOnlyHint=true already covering safety, the description adds useful behavior: data is fetched live, results are grouped by provider statuses, and the default is open tickets only. It does not disclose pagination, rate limits, per-account auth requirements, or what a ticket record contains.

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 source, ownership scope, grouping, and default all packed in without wasted words. Every clause earns its place.

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 four-parameter, no-output-schema list tool, the description covers the data source and grouping but omits return shape details beyond grouping, pagination behavior, and how account scope interacts with results. Adequate but with clear gaps.

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 75%, so the schema already explains status matching, account selection, channel enum, and include_done. The description adds only the default-open behavior, which implicitly relates to include_done, but it doesn't clarify the account or status filter semantics beyond what the schema provides.

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 and resource ('List the user's own tickets') and names the sources ('live from Jira / ClickUp'), which is enough to distinguish it from the singular sibling get_ticket. It doesn't explicitly contrast itself with list_accounts or the conversation tools, so it stops short of a 5.

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?

Usage is implied by 'list' and by the default 'open ones', but the description never states when to choose this over get_ticket for a single ticket or when to broaden with include_done. No explicit alternatives or exclusions are given.

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