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

The description provides valuable behavioral details like 'bounded previews and delivery status.' This informs the agent about the specific data points returned, complementing the structural safety hints provided in the annotations.

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?

The description is a single, highly efficient sentence that packs the resource type, scope, and data features into minimal space.

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?

Given that the output schema exists, the description is complete enough by defining the scope and the nature of the included information (previews and status) for an agent to correctly invoke and interpret the results.

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?

With 0% schema description coverage, the description must compensate. It mentions 'bounded previews,' which implies the need for pagination control, but it does not explicitly define the role or expected range of the 'pageSize' parameter beyond the schema.

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 clearly defines the resource (support tickets), the action (lists), and the scope (the connected user’s own tickets), which effectively differentiates it from sibling tools like create_support_ticket.

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?

While the 'user's own' qualifier provides a scope for usage, the definition does not explicitly state when to use this tool over other potential list or search mechanisms.

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