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

readOnlyHint=true already tells the agent this is a safe, non-destructive read, so the description need not restate that. It adds the underlying REST endpoint (GET /api/v2/people/{id}/tickets), which is modestly useful context, but says nothing about pagination behavior, result volume, or what 'no tickets' looks like.

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 stating the action and scope, followed by the endpoint reference. No filler, no redundancy with the title or schema.

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 low-complexity read tool with full schema coverage and a readOnlyHint, the description covers the essentials. The main omission is return shape — with no output schema, the agent gets no hint whether the response is a bare array or a paginated envelope with totals.

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 100%, with page, count, and person_id all documented in the schema itself (including the 1-200 range on count). The description adds only the implicit notion that person_id identifies the person whose tickets are returned, matching the baseline 3 when the schema carries the load.

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?

Specific verb ('List') and resource ('tickets') with an explicit scope qualifier: 'raised by one person'. That scope naturally separates it from deskpro_list_tickets and deskpro_list_organization_tickets, though those siblings are never named outright.

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?

'their support history' implies the use case of reviewing one person's past tickets, but there is no explicit when-to-use statement and no exclusion or alternative routing (e.g., use deskpro_list_tickets for a broad feed). Usage must be inferred from the phrasing.

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