easypost_get_trackerRetrieve a single tracker by id, including current status and tracking_details history. API: GET /trackers/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Tracker id, e.g. trk_... |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, confirming read-only operation. Description adds API endpoint but no additional behavioral traits (e.g., error handling, authentication, rate limits). With annotations, bar is lowered; description adds minimal 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 concise sentences, each with clear purpose: first states action and output, second provides API reference. No redundant 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?
Tool has one parameter and annotations, but no output schema. Description does not elaborate on response structure, error cases, or pagination. Adequate for a simple retrieval but could include typical failure modes.
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% for the single parameter 'id', already described with example format. Description only reiterates 'by id', adding no new meaning beyond 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?
Description specifies verb 'Retrieve', resource 'tracker by id', and includes output details ('current status and tracking_details history'). Clearly distinguishes from listing or creating trackers.
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?
Description implies use when a specific tracker id is known, but does not mention when to prefer this over list_trackers or create_tracker, nor any exclusions or alternatives.
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.