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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally. The description adds that results are paginated, which is useful behavioral context, but says nothing about ordering, cursor semantics, or result volume. With annotations carrying the safety load, this is an adequate but not rich disclosure.

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 brief sentences, front-loaded with the operation and scope; nothing is padded or repeated. The endpoint reference is compact and informative for an agent that may need to map to API docs.

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 simple, read-only, zero-required-param list tool with full schema coverage and no output schema, the description covers enough to invoke it correctly. There is no output schema, so the description need not explain returns, though it could note the address fields returned.

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 after_id, before_id, and page_size are fully documented in the schema itself. The description only alludes to pagination generically and adds no syntax or semantic detail beyond what the schema already provides, which is the baseline-3 case.

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 states a specific verb and resource ('List saved addresses on the account') plus the underlying endpoint, so the agent knows exactly what the tool does. It does not, however, explicitly distinguish itself from sibling easypost_get_address or easypost_list_shipments.

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?

Usage is only implied by the word 'List' and the account scope; there is no statement of when to reach for this tool versus easypost_get_address (single lookup) or the other list tools. No exclusions or prerequisites are given.

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