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

The readOnlyHint annotation already establishes that this is a non-mutating read, so the bar is lower. The description adds the underlying API call (GET /trackers), which is mildly useful, but says nothing about pagination behavior, default page size, or result volume — meaningful gaps for a list operation.

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?

A single efficient sentence with the filter semantics front-loaded, followed by the raw API endpoint. Nothing is padded, though the API path line carries little decision value 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?

There is no output schema, so the description would ideally characterize the returned tracker list or pagination semantics, and it does not. For a simple read-only list tool this is adequate but leaves the agent without return-shape or paging expectations.

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 three parameters are already documented in the schema. The description only restates that tracking_code and carrier act as filters and omits page_size entirely, adding no syntax or format detail beyond the schema. 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 and resource ('List package trackers') plus the optional filter dimensions, so the operation is unambiguous. It does not name or differentiate itself from the sibling easypost_get_tracker (single vs. list), which is the main remaining gap.

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?

The description only says the listing is 'optionally filtered by tracking_code or carrier' — it never states when to use this list tool versus easypost_get_tracker or easypost_create_tracker, nor any pagination caveat. Usage is left entirely to inference from the name.

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