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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds value by disclosing sort order (newest first), the field set returned, the backing endpoint (GET /api/manifests), and an explicit boundary that manifest creation is not available here. It does not mention pagination behavior, though the schema's next_page reference implies it.

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 compact sentence carries purpose, scope, ordering, and return fields, with the scope constraint front-loaded; the read-only/negative clause follows immediately. Nothing is padded.

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 usefully enumerates the returned fields (number, date, carrier, package/consignment counts), which is exactly the compensation needed. Two optional params are schema-documented. Only pagination semantics are left entirely to the schema, a minor gap for a simple list tool.

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 100% — page and limit are fully documented in the schema, including defaults and the next_page chaining pattern. The description adds no syntax or format detail beyond that, 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?

States a specific verb and resource ("List manifests"), a precise scope ("already submitted to carriers"), ordering ("newest first"), and the returned fields (number, date, carrier, counts). An agent can distinguish this from every sibling listing tool (orders, pickups, products, tags) without opening a schema.

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 scope phrase "already submitted to carriers" combined with "Read only; manifesting is not available here" implies when this applies (reviewing submitted manifests) and rules out a write-oriented expectation. However, it names no alternative tool or condition for choosing between this and, say, list_pickups; usage is implied rather than stated.

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