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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful detail by enumerating the returned fields (id, number, date, name, carrier, tracking number, country), which matters since there is no output schema. It says nothing about matching behavior (exact vs substring vs fuzzy on 'phrase'), which is a meaningful gap for a search tool.

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 compact sentences plus the endpoint path, with the query capability front-loaded before the return shape. No filler and nothing redundant with the name.

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?

Because no output schema exists, the enumerated return fields are essential and present. Search semantics (matching mode) and any distinction from the list_* siblings remain unspecified, but for a read-only search endpoint whose annotations carry the safety profile, the description is nearly complete.

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%, so all six parameters including enums and pagination are fully documented in the schema. The description only restates the search-field and status concepts already present there, adding no syntax, format or defaulting detail. 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 (search) and resource (orders) and enumerates the searchable fields plus the optional status restriction. However, it never distinguishes itself from siblings like starshipit_list_orders, starshipit_list_unshipped_orders or starshipit_list_shipped_orders, which overlap heavily with the status filter described here.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no sibling is named. The agent must infer that a free-text phrase is the trigger for this tool rather than one of the several list_* order tools, even though 'optionally limited to unshipped or shipped orders' makes it a functional duplicate of two siblings.

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