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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. With no output schema, the description usefully enumerates the returned columns (contact, country, carrier, weight, manifest, dates) and the aggregate counts, but adds no auth, pagination or rate-limit context.

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 sentences with no filler, and the scoping constraint plus return contents are front-loaded. The first sentence is dense to the point of being a run-on, which slightly hurts scanability.

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 read-only listing tool with annotations covering safety and no output schema, the description supplies the returned fields and the aggregate counts, which is what an agent needs. Filtering, sorting and pagination are covered by the schema, leaving little gap.

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 83% and the filter/sort parameters are thoroughly documented in the schema itself, so the schema carries the load. The description reinforces that filtering and sorting are supported and lists the four statuses, 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 action and resource — a compact order list scoped to one status plus account-wide counts — and front-loads its distinguishing feature (compact + aggregate counts) versus the plain list siblings. It never names the sibling it should be chosen over, so it stops short of full differentiation.

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?

Only 'Supports filters and sorting' is offered; there is no when-to-use versus starshipit_list_orders, starshipit_search_orders, or the per-status list tools, and no when-not conditions. Usage is implied by the word 'summary' at best.

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