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

Annotations only declare readOnlyHint=true, so the description adds real value: ordering (newest first), result scope (all channels, all time, including cancelled), and an auth requirement. It also discloses that it renders an interactive shipments card, which is behavior an agent cannot infer from structured fields.

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?

Front-loaded with the core purpose and scope in the first two sentences; the auth note and card-rendering detail follow. Every sentence carries information, though the UI-rendering sentence is the least load-bearing for an agent.

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 appropriately covers return scope and ordering, and the readOnlyHint annotation plus the stated auth requirement cover the safety profile. Pagination behavior is only in the schema's limit description, a minor gap for a tool this simple.

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% and there is a single optional limit parameter fully documented in the schema, so the baseline is 3. The description's 'newest first' hints at ordering but adds no syntax or format detail beyond the schema.

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 recent bookings for this API key, newest first') and explicitly contrasts its scope with the sibling shipper_profile, so an agent can distinguish it without opening any 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?

Names the alternative (shipper_profile) and precisely characterizes the scope difference — all channels, all time, including cancelled, versus 180-day non-cancelled agent-API counts — giving clear context for selection. It stops short of stating an explicit when-not rule, but the comparison is strong routing guidance.

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