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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the status lifecycle, the included counts and timestamps, and the filtering options. No contradictions with annotations.

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 succinct sentences: the first states the core purpose and returned data, the second covers filtering. Every word adds value, no redundancy, and the key information is front-loaded.

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?

The tool has 5 optional parameters, an output schema, and read-only annotations. The description adequately explains the manifest lifecycle, included data, and filter options. Minor ambiguity about whether all statuses are included or just a subset, but the arrow notation implies all three stages.

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 80%, so the schema already documents most parameters. The description restates the filter capabilities (warehouse, date range) but does not add meaning beyond what the schema provides. Offset lacks a description in schema, and the description does not clarify it either, so this is baseline 3.

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 clearly identifies the tool as listing courier hand-over manifests, specifying the lifecycle stages (draft → submitted → acknowledged) and what data is included (shipment + order counts, timestamps). This distinguishes it from sibling tools like get_manifest (singular) and other list tools.

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 description explicitly states the available filters (warehouse and date range), giving clear context for when to use this tool. It does not explicitly mention alternatives or when not to use it, but the existence of get_manifest for single-record details is implied by the sibling list.

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