list_manifests

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

The readOnlyHint already establishes this is a non-mutating read, so the description's job is lighter. It adds the useful detail of which fields come back, but says nothing about result volume, pagination, ordering, or whether all manifests are always returned — notable gaps for a parameterless list tool.

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 with no filler; every word (verb, resource, returned fields) carries information. Nothing could be trimmed without losing content.

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 parameters and no output schema, the description partially compensates by naming the returned fields, which is genuinely useful. However, it omits the operational facts an agent would want for a parameterless list call — whether results are paginated, capped, or ordered — leaving the definition only marginally complete.

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?

There are zero input parameters, so there is nothing for the description to disambiguate; baseline is 4. The enumerated fields are output-side information rather than parameter semantics, which is a bonus rather than a requirement here.

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 specific verb ('List') and resource ('manifests') and enumerates the fields the listing includes (id, aircraft, route, leg, status, arrival date). It is clearly distinct from get_manifest by name, but the description itself does not explicitly contrast the two.

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: an agent can infer this is the bulk-listing counterpart to get_manifest, but the description never says when to use this versus get_manifest or any filtered alternative. No prerequisites or exclusions are stated.

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