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

readOnlyHint=true already tells the agent this is a safe read. The description adds the underlying REST endpoint, which helps a Deskpro-aware caller, but says nothing about ordering, result shape, or how the person_id must relate to an existing person. Given the annotations carry the safety profile, this is adequate but not rich.

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?

Two short sentences, front-loaded with the core purpose and with no filler. The endpoint reference is mildly redundant for an agent but cheap and useful for mapping to the API.

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 simple read-only list endpoint with fully documented parameters and a safety annotation, the description covers what the agent needs to select and call it. It does not restate return values, which is acceptable with no output schema, though pagination behavior is left entirely to the schema.

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%, so page, count, and person_id are all documented in the schema; the baseline is 3. The description only restates the person scoping ('one person') and adds no format or constraint detail 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 states a specific verb (List) and resource (tickets) plus the scoping axis (raised by one person, i.e. a support history), which naturally separates it from deskpro_list_tickets and deskpro_list_organization_tickets. It stops short of naming those siblings explicitly, so the differentiation is inferable rather than stated.

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" hints at the use case — pulling one contact's ticket log — but there is no explicit when/when-not guidance and no named alternative (e.g. use deskpro_list_tickets for a global feed). Usage is implied rather than spelled out.

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