list_persons

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It says nothing about result caps, pagination, ordering, or whether a missing search term returns everything — the main behavioral questions for a list tool remain unanswered.

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?

One short sentence with zero filler, leading with the action and resource. Nothing could be trimmed without losing scope information.

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 with one optional parameter and no output schema, the description is minimally sufficient to call the tool. It still leaves open whether results are paginated or complete, which matters when deciding whether to filter server-side.

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 coverage is 100% with a single optional "search" parameter already described as a "Name substring filter." The description adds no further meaning about matching behavior, but the schema carries the burden fully, so the 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?

"List saved persons (passengers/crew) with their ids" gives a specific verb and resource, and clarifies the domain objects plus what is returned. It is distinguishable from siblings like get_person and create_person, though it never names them explicitly.

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?

There is no guidance on when to use this versus get_person, nor whether it is meant for lookup-by-id or browsing. The phrase "with their ids" faintly hints the tool is a discovery step, but that is inference rather than instruction.

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