get_manifest

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

readOnlyHint=true already declares the safety profile, so the description's job is to add context. It does disclose the shape of the payload (flight fields plus occupants with name, duty, US address), which hints at sensitive personal data, but it never states that the response contains PII or what happens if the id is unknown. Modest added value over the annotation.

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, front-loaded with the action and then the payload, with zero filler. It is arguably too terse given the under-specified id, but nothing in the wording is wasted.

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 single-parameter read tool with no output schema, the description roughly maps the return payload, which is the main gap it needed to fill. However, it leaves the id's referent ambiguous and gives no guidance for choosing it over list_manifests, so it is only adequate.

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 is a single required parameter, id, with 0% schema description coverage, so the description must explain it. It implies the id identifies a manifest via the singular 'a manifest' framing, but never states which entity the id refers to (manifest, flight, or draft) or its format. Partial compensation only.

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 names a specific verb and resource ("Get a manifest") and enumerates the returned content — flight fields and occupants with name, duty, US address — which tells an agent what this tool surfaces. It does not explicitly distinguish itself from list_manifests or get_person, so routing relies on the singular phrasing plus the id parameter.

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 list_manifests (browse) or create_manifest_draft/update_manifest (mutation), and no prerequisites or exclusions. The 'Get' verb implies retrieval, but the choice among the manifest siblings 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.