easypost_list_trackersList package trackers, optionally filtered by tracking_code or carrier. API: GET /trackers.
| Name | Required | Description | Default |
|---|---|---|---|
| carrier | No | Filter by carrier name, e.g. USPS, UPS, FedEx. | |
| page_size | No | Results per page (max 100). | |
| tracking_code | No | Filter by carrier tracking code. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true; description adds the API endpoint (GET /trackers) for context but lacks details on pagination, rate limits, or auth.
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 concise sentence with an API reference; no unnecessary words.
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?
Describes the primary function and filter options but omits pagination behavior (despite page_size parameter) and expected response format.
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% with parameter descriptions; the description only reiterates the filtering capability without adding new meaning.
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 states 'List package trackers' with optional filters, distinguishing it from sibling tools like get_tracker or create_tracker.
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?
Mentions optional filters but does not explicitly guide when to use this tool versus alternatives (e.g., single tracker retrieval). Sibling context is available but not leveraged.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: address operations, shipment lifecycle (create, buy, refund, get, list), and tracking. No overlap or ambiguity.
All tools follow a consistent `easypost_<verb>_<resource>` pattern using snake_case, with clear verbs like create, get, list, buy, refund, verify.
11 tools cover the essential operations for address management, shipment lifecycle, and tracking without being too many or too few.
Core workflows (rate, buy, refund, track, address verification) are complete. Minor gaps like missing delete for addresses or update for shipments are acceptable for the domain.