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

Annotations already establish readOnlyHint=true, so safety is covered. The description adds genuine behavioral value by disclosing the shape of the result (name, emails, phones, organization, labels, custom fields, ticket count), which matters because there is no output schema. It still says nothing about permissions or error behavior (e.g., unknown id).

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 sentences, front-loaded with the action and result contents. The trailing REST endpoint reference is mildly redundant with the tool name and of limited value to an agent, but it costs little.

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?

With no output schema, enumerating returned fields is exactly the right compensation, and the schema fully documents the two inputs. Missing only edge-case behavior (not-found handling, whether `include` affects cost/size), which keeps it short of a 5.

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%, including the sibling-loading `include` parameter with examples, so the schema carries parameter meaning fully. The description only restates the id lookup and adds no syntax or constraint detail beyond it; baseline 3 applies.

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 concrete verb+resource ("Fetch a single person by id") and enumerates the payload fields returned. The word "single" implicitly separates it from deskpro_list_people, but no sibling is named explicitly, so the differentiation is inferential 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?

Usage is only implied: by requiring an id, the description suggests it is used when the id is already known, versus list_people or search. There is no explicit when-to-use, when-not-to-use, or alternative named, which is a real gap given three sibling read tools could plausibly be chosen instead.

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