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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds content-level context about what the listed entries contain (expertise, will/won't answer, SLA, price), which is genuinely useful, but says nothing about pagination, filtering, or result format.

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 tight fragment with no filler, and the key information ('who can be asked') is front-loaded. It reads as a data gloss rather than a sentence, which slightly weakens it as a standalone purpose statement.

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, the description must characterize the return values, and it does so by naming the four field types each person entry carries. For a zero-param listing tool this is close to sufficient, though it omits any statement about the number of results or ordering.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 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?

The title supplies the verb+resource ('List the people'), and the description enumerates the specific fields returned (expertise, SLA, price), so the resource is concrete. It is distinguishable from ask_person/get_answer by implication (discovery vs. interrogation), but the description itself never states a verb or explicitly contrasts with the siblings.

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?

The phrase 'Who can be asked' hints at a discovery step preceding ask_person, but there is no explicit when-to-use statement, no condition selecting it over ask_person or get_answer, and no exclusions. Guidance is left entirely to inference.

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